From b86b9207bc52514df472f6458d79ea5421a312fb Mon Sep 17 00:00:00 2001 From: Rohit Yadav Date: Mon, 31 May 2021 14:03:36 +0530 Subject: [PATCH 1/3] systemvm: document workaround for older ACS env with systemvms Signed-off-by: Rohit Yadav --- source/upgrading/upgrade/_sysvm_restart.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/source/upgrading/upgrade/_sysvm_restart.rst b/source/upgrading/upgrade/_sysvm_restart.rst index 8f01fb2299..93bd622110 100644 --- a/source/upgrading/upgrade/_sysvm_restart.rst +++ b/source/upgrading/upgrade/_sysvm_restart.rst @@ -26,6 +26,22 @@ from the new systemVM template version. or do it by using third-party tools such as Ansible. Below we are giving instructions for using the "cloudstack-sysvmadm" script. +Note: When upgrading from older CloudStack environments (for example, 4.9-4.13) +with XenServer or XCP-ng hosts, some systemvms and virtual routers may not have +ejected or removed the older systemvm.iso. The old systemvm.iso needs to be +ejected and removed before new systemvms and virtual routers are (re-)created). +This issue has been fixed in CloudStack 4.15, older enviroments may need the +following to be run on the XenServer or XCP-ng pool master: + +.. parsed-literal:: + + # for vm in $(xe vm-list | grep name-label | sed 's/.*name-label.*: //g'); do + if [[ $vm == [rvs]-* ]]; then + echo "Attempting systemvm.iso eject and remove for $vm"; + xe vm-cd-eject vm=$vm; + xe vm-cd-remove vm=$vm cd-name=systemvm.iso; + fi; + done Ensure that the admin port is set to 8096 by using the "integration.api.port" global parameter. This port From ea4296af111c129df8a628fcbd9ded3f9d8da3c4 Mon Sep 17 00:00:00 2001 From: Rohit Yadav Date: Mon, 31 May 2021 14:05:02 +0530 Subject: [PATCH 2/3] Update _sysvm_restart.rst --- source/upgrading/upgrade/_sysvm_restart.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/upgrading/upgrade/_sysvm_restart.rst b/source/upgrading/upgrade/_sysvm_restart.rst index 93bd622110..e8bdd09b07 100644 --- a/source/upgrading/upgrade/_sysvm_restart.rst +++ b/source/upgrading/upgrade/_sysvm_restart.rst @@ -30,8 +30,8 @@ Note: When upgrading from older CloudStack environments (for example, 4.9-4.13) with XenServer or XCP-ng hosts, some systemvms and virtual routers may not have ejected or removed the older systemvm.iso. The old systemvm.iso needs to be ejected and removed before new systemvms and virtual routers are (re-)created). -This issue has been fixed in CloudStack 4.15, older enviroments may need the -following to be run on the XenServer or XCP-ng pool master: +This issue has been fixed in CloudStack 4.15, upgrading from older enviroments +may need the following to be run on the XenServer or XCP-ng pool master: .. parsed-literal:: From 8f8b9edf6aa8e979b97f82e24c7394f277d72fe4 Mon Sep 17 00:00:00 2001 From: Rohit Yadav Date: Mon, 31 May 2021 14:11:18 +0530 Subject: [PATCH 3/3] Update source/upgrading/upgrade/_sysvm_restart.rst Co-authored-by: Abhishek Kumar --- source/upgrading/upgrade/_sysvm_restart.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/upgrading/upgrade/_sysvm_restart.rst b/source/upgrading/upgrade/_sysvm_restart.rst index e8bdd09b07..f127b1fb72 100644 --- a/source/upgrading/upgrade/_sysvm_restart.rst +++ b/source/upgrading/upgrade/_sysvm_restart.rst @@ -30,7 +30,7 @@ Note: When upgrading from older CloudStack environments (for example, 4.9-4.13) with XenServer or XCP-ng hosts, some systemvms and virtual routers may not have ejected or removed the older systemvm.iso. The old systemvm.iso needs to be ejected and removed before new systemvms and virtual routers are (re-)created). -This issue has been fixed in CloudStack 4.15, upgrading from older enviroments +This issue has been fixed in CloudStack 4.15, upgrading from older environments may need the following to be run on the XenServer or XCP-ng pool master: .. parsed-literal::