Manage the upgrade
Perform this task to manage software images, including upload software images, and create and run
an upgrade task.
Restrictions and guidelines
• If the upgrade targets of an existing upgrade task include the primary and standby CVM nodes (not in the cluster), you can add the nodes to the cluster only after you delete that upgrade task.
• If the management-node hosts and service-node hosts on the platform require separate upgrade, you must upgrade the management-node hosts before upgrading the service-node hosts.
• If the management platform manages both x86 and ARM hosts, you must select hosts of each architecture for separate upgrade.
• To ensure successful precheck before you run an upgrade task, disable HA on the Cluster Name > Configure > HA page.
• Perform upgrade operations when the management platform does not run tasks. If the management platform is running a task and you perform an upgrade operation, the task might fail.
• The management platform excludes low-version hosts when selecting upgrade targets for adding an upgrade task.
• When you upgrade the management platform, the system will enter the static upgrade page that displays the detailed upgrade process. After the upgrade completes, the page closes. After the management platform service restarts, manually refresh the page to access the login page. If a restart is required in host upgrade and automatic migration is enabled, hosts might automatically restart. After the hosts restart and restore, the management platform interface opens again.
• After you upgrade hosts and access the upgrade process page, if a host unexpectedly power cycles, you must re-enter the management platform IP or clear the browser cache after the host restores to access the management platform interface again.
• Deleting a host also deletes the corresponding upgrade target. If the upgrade target is running, deletion is prohibited.
• If the host is a primary/standby node, while deleting this host, the system will simultaneously clear the upgrade target information associated with this primary/standby node.
• After you configure automatic VM migration, if the host reboot times out, the system prompts partial success of the upgrade task in the task console or in the upgrade report. In this case, you must identify whether the host has rebooted successfully (by using the ping command or accessing the remote console) and then manually exit the maintenance mode. If the host has successfully restarted, manually configure the host to exit the maintenance mode. If the host does not restart, manually restart the host through the remote console, and then manually configure the host to exit the maintenance mode.
• Before performing a version upgrade online, execute the which ovs-hdpuctl command in the host backend. If the output is /usr/bin/ovs-hdpuctl, the command exists, and OVS supports the in-service upgrade feature during version upgrades. On the contrary, this feature is not supported. In addition, the in-service OVS upgrade feature is not supported in DPDK scenarios, S1020V scenarios, or cross-kernel version upgrades.
Features
• Manage the repository
• Manage upgrade tasks
Manage the repository
Upload an upgrade/patch package
To upgrade the management platform or install a patch, perform this task to upload the required file to the management platform for centralized management.
-
On the top navigation bar, click System.
-
From the left navigation pane, select Upgrade Management.
-
Click the Repository tab.
-
Click Upload.
-
Click in the dashed box and select the desired upgrade/patch package in the dialog box that opens. You can also directly drag and drop the desired upgrade/patch package into the dashed box.
-
Click Start. After the package is uploaded, you can see it on the upgrade management page.
-
On this page, you can view detailed information about the uploaded upgrade/patch packages.
○ Name: Name of the uploaded upgrade/patch package.
○ Software Image Type: Type of uploaded package.
▪ Patch Version: The uploaded package is a patch.
▪ Full Version: The uploaded package is an upgrade package.
○ Published At: Time when the upgrade/patch package was uploaded to the management platform.
○ Compatibility: Whether the upgrade/patch package is compatible with the current management platform version.
Manage upgrade tasks
About this task
After you upload an upgrade or patch package to the management platform, perform this task to create an upgrade task to manage the upload or patch package. You can run an upgrade task immediately, precheck upgrade targets, view detailed information about, edit, and delete an upgrade task, distribute an upgrade package, and view upgrade logs.
Restrictions and guidelines
• During the upgrade and rollback process, do not operate the upgraded hosts or resources of the hosts. If you upgrade/roll back the management platform, do not operate all resources.
• After the upgrade, rollback is not supported if you have performed service operations such as modifying the upgraded hosts or their VMs.
• If a VM on a NingOS 2.0 host uses the io_uring disk I/O mode, change the mode to native or thread before the upgrade.
Features
• Add an upgrade task
• Run an upgrade task immediately
• Distribute an upgrade/patch package
• Precheck upgrade targets
• Edit an upgrade task
• Delete an upgrade task
• Finish an upgrade task
• View detailed information about an upgrade task
• Download upgrade logs
• Uninstall a patch
• Manage rollback
Add an upgrade task
About this task
After you upload an upgrade or patch package to the management platform, perform this task to create an upgrade task to upgrade hosts.
Procedure
-
On the top navigation bar, click System.
-
From the left navigation pane, select Upgrade Management.
-
Click the Upgrade Task tab.
-
Click Add Task.
-
Configure the parameters.
-
Click OK.
Parameters
• Task Name: Enter the name of the upgrade task.
• Description: Enter the description for the upgrade task.
• Software Image: Select the target upgrade version. Available versions depend on the upgrade/patch packages uploaded to the repository.
• Upgrade Target: Select the hosts to be upgraded. You can select a data center or cluster to select hosts in bulk. Management hosts are identified with CVM. For full version upgrade, you must select all nodes in the cluster. Upgrading hosts on management platform will temporarily cause the management platform to be unavailable.
Run an upgrade task immediately
After creating an upgrade task, you can perform this task to upgrade hosts or install a patch for the
hosts on the management platform.
-
On the top navigation bar, click System.
-
From the left navigation pane, select Upgrade Management.
-
Click the Upgrade Task tab.
-
Click Run Now in the Actions column for an upgrade task.
-
Before you run an upgrade task, distribute the package to and precheck all upgrade targets.
○ Distribute: Push the upgrade/patch package to the target hosts in advance to avoid long wait time during the upgrade. In the Distribute window, click Distribute to
Distribute an upgrade/patch package
Precheck upgrade targets
The system performs a check before the upgrade to confirm whether all target hosts meet the upgrade
conditions. If a host fails the check, the system displays the reason for troubleshooting.
- On the top navigation bar, click System.
Edit an upgrade task
Delete an upgrade task
Perform this task to delete an upgrade task and related settings from the management platform.
-
On the top navigation bar, click System.
-
From the left navigation pane, select Upgrade Management.
-
Click the Upgrade Task tab.
-
Click More in the Actions column for the target upgrade task, and then select Delete.
Finish an upgrade task
View detailed information about an upgrade task
Perform this task to view detailed parameters and settings of an upgrade task.
-
On the top navigation bar, click System.
-
From the left navigation pane, select Upgrade Management.
-
Click the Upgrade Task tab.
Download upgrade logs
Uninstall a patch
About this task
Perform this task to remove or disable installed patches without rolling back or reinstalling the major version. This restores the system to the original state of the current major version. Use this feature to
Manage rollback
About this task
When a serious issue (such as a security vulnerability, operation failure, or critical feature defect) occurs during an upgrade, this feature quickly restores the system to a previous stable full version without system reinstallation. It limits the available rollback time via the rollback window and records details of the rollback process in rollback logs. You can download the logs for troubleshooting and auditing. This feature is applicable to scenarios where an upgrade causes service anomalies, degraded performance, or unexpected faults, and where the rollback process must be traced to meet compliance and audit requirements.
Features
• Roll back a full version
• Set the rollback window
• Download rollback logs
Roll back a full version
About this task
Perform this task to restore the system to a previous stable version without system reinstallation, helping address emergency issues such as security vulnerabilities, operation failures, and defects of major functions, thereby quickly restoring the continuous and stable operation of the system.
Restrictions and guidelines
• During the rollback process, do not perform any operations on the Web interface.
• After a successful rollback, if a restart is required in host upgrade, you must manually restart hosts.
• A full version only supports rollback at the cluster level. If all hosts in a cluster have been upgraded successfully, rollback is not supported.
• Version rollback cannot be performed in the following conditions:
○ The version of a host added to the platform is earlier than the platform version. To roll back the host version, first upgrade the host version to the platform version.
○ The host database is damaged.
○ The stateful failover system is unstable.
○ Backup data is lost. (Backup data is stored in the /vms/upgrade_backup path of a host.)
• To roll back the version of a CVK host at the CLI, first upload the upgrade package to the CVK host and decompress it.
• To perform version rollback at the CLI after a primary/standby switchover in a stateful failover environment, first upload the upgrade package to the upgraded management platform host and decompress it.
• In a stateful failover environment, after the upgrade is completed at the CLI or on the Web interface of the management platform, version rollback is allowed only if the primary and standby node roles are consistent with those before the upgrade.
Procedure
-
On the top navigation bar, click System.
-
From the left navigation pane, select Upgrade Management.
-
Click the Upgrade Task tab.
-
Select an upgrade task. The lower part of the page displays the upgrade status of each upgrade target in that task.
-
Select the desired upgrade targets, and then click Roll Back.
-
In the dialog box that opens, click OK.
Set the rollback window
Download rollback logs
Perform this task to save detailed records of host rollback locally, including information such as
upgrade targets, rollback results, and failure reasons. You can use the logs for troubleshooting, operations auditing, and rollback history retention.
-
On the top navigation bar, click System.
-
From the left navigation pane, select Upgrade Management.
-
Click the Upgrade Task tab.
-
Select an upgrade task. The lower part of the page displays the upgrade status of each upgrade target in that task.
-
Click Rollback Log in the Actions column for the desired upgrade target.