Updated on 2024-07-16 GMT+08:00

Changing an OS

Scenarios

If the OS running on the cloud server in a FlexusL instance cannot meet service requirements, you can change the OS to another OS version or type.

Notes

  • To change the OS using a private image, learn about the constraints and usage of private images first by referring to Managing Private Images.
  • An OS change does not make any changes to server specifications.
  • After the OS is changed, the server IP address remains unchanged.
  • Data in all partitions (including the system partition) of the system disk will be cleared, so you are advised to back up the system disk data prior to an OS change.
  • An OS change does not affect data in data disks.
  • After the OS is changed, the original OS is not retained.
  • After you change the OS, you need to deploy services in the new OS.
  • After the OS is changed, the server automatically starts.
  • Do not reset the password of, restart, or stop the FlexusL instance immediately after the OS is changed. Wait for several minutes until the system successfully injects the password, or the login will fail.

Constraints

Billing

An OS change does not involve refund or supplementary payment.

Procedure

  1. Log in to the FlexusL console and click a resource card to go to the instance details page.
  2. Change the OS using any of the following methods.
    • Method 1: Locate the target FlexusL instance, choose > Change OS.
    • Method 2: On the Overview page, choose > Change OS in the upper right corner.

    • Method 3: On the Cloud Servers page, choose > Change OS in the row containing the target server.

    • Method 4: On the Cloud Servers page, click the target server name. In the upper right corner of the displayed page, choose > Change OS.
  3. Specify the parameters required for changing the OS.

  4. Click Submit.

    After the OS is changed, the server automatically starts. When the server status is Running, the OS change is complete.

    • Do not reset the password of, restart, or stop the FlexusL instance immediately after the OS is changed. Wait for several minutes until the system successfully injects the password, or the login will fail.
    • After the OS is changed, the login password is cleared. You need to reset the password for logging in to the new OS. If you switch to an application image, reset the password only after the image with the pre-installed application is up and running, or the password reset may fail.