Hello, Sanjay First, it is important to highlight that the 4.21.0.0 ACS version, according to [1], was released with a blocker issue for KVM-based environments. The issue seems to be occurring for environments with the physical networks containing the Storage traffic type [2]. Therefore, it is recommended to first test and validate the 4.21 version in a staging environment.
As for the upgrade process, when updating ACS to a new major version, it is required for the system VM template of the new version to be either included in the new version packages or to be manually registered before starting the upgrade process. The ACS documentation section [3] contains instructions to manually register it. After the registration of the SSVM template is completed, the upgrade process can be started. ## Management Servers Upgrade Before upgrading the Management Servers, UI customizations files (such as logos and banners) located in `/usr/share/cloudstack-management/webapp/` should be backed up. Next, the following steps can be executed: 1. Ensure there are no running asynchronous jobs by executing the `listAsyncJobs` API with the parameter `listall=true` 2. Stop the `cloudstack-management` and `cloudstack-usage` services on all Management Server nodes 3. Dump the `cloud` and `cloud_usage` databases [4] 4. Install the new packages (`cloudstack-management`, `cloudstack-ui`, `cloudstack-usage` and `cloudstack-common`) only on one Management Server node 5. Start and monitor the upgrade process in the updated node 6. Validate API and UI access 7. Repeat steps 4 and 5 for the other Management Server nodes ## Agent Upgrade To update the Agent service in the KVM compute plane hosts, the following steps can be executed: 1. Stop the `cloudstack-agent` service 2. Install the new packages (`cloudstack-common` and `cloudstack-agent`) 3. Start the `cloudstack-agent` service ## Post Upgrade After the upgrade is completed, the system VMs should be recreated. To recreate the CPVM and SSVM, it is simply required to delete the existing ones, and the Management Server will provision the new ones with the correct system VM template. For VRs, it is required to clean up VPCs and isolated and shared networks. Best regards, Bernardo De Marco Gonçalves (bernardodemarco) [1]: https://github.com/apache/cloudstack/issues/11552 [2]: https://github.com/apache/cloudstack/issues/11552#issuecomment-3250671946 [3]: https://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-4.21.html#update-system-vm-templates [4]: Dumps can be used to roll back the upgrade if any problems are encountered during the installation. To roll back, all Management Server nodes should be stopped. Next, the dumps can be restored and the packages of the version to be rolled back to can be reinstalled. Em seg., 8 de set. de 2025 às 07:38, Sanjay Kumar <[email protected]> escreveu: > Hell0! > > We are planing to upgrade my infra from 4.20 to 4.21 so is there any > discrepancy during the upgradation? what is proper step to complete my > upgrade without any issue? > > Any help would be really appreciated. > > Thank you >
