No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


HUAWEI CLOUD Stack 6.5.0 Alarm and Event Reference 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
1060039 Failed to Change the Disk Type

1060039 Failed to Change the Disk Type


Failed to change the disk type.



Alarm Severity

Auto Clear








Indicates the event ID.

Object Type

Indicates the event type.

Generated At

Indicates the last time the event was generated.

Fault Location Info


Indicates the ID of the tenant who is performing an operation when the event is generated.


Indicates the ID of the EVS disk for which the event is generated.


Indicates the ID of the task for which the event is generated.

Additional Info


Indicates the service name.


Indicates the microservice name.


Indicates the operation name.


Indicates the error phase.


Indicates the error message.

Impact on the System


Possible Causes

  • The connection to FusionSphere OpenStack Cinder is abnormal.
  • FusionSphere OpenStack Cinder fails to retype the volume type of an EVS Disk.
  • The link between FusionSphere OpenStack Cinder and Storage is disconnected.


  1. Log in to ManageOne Maintenance Portal using a browser.

    • The login address is https://Address for accessing ManageOne Maintenance Portal:31943, for example,
    • Default username: admin; default password: Huawei12#$

  2. In the navigation tree, choose Alarms > Event Logs. Click Filter to filter the event based on the event name.
  3. Query the following alarm information:

    • Fault Location Info (including VolumeID, TenantID, and JobID)
    • Additional Info
    • Generated At

  4. If a joint locating with other components is required and the alarm information does not provide information for locating faults occurred on other components, obtain the location information from the log. If no, skip this step.

    1. Use PuTTY to log in to the CPT-SRV01 node using the IP address corresponding to the CPT-SRV01 field (searching in the xxx_export_all_EN.xlsm file) and log in to the CPT-SRV02 node using the IP address corresponding to the CPT-SRV02 field (searching in the xxx_export_all_EN.xlsm file).

      Default account: apicom, default password: Huawei12#$

    2. Run the following command and enter the password of user root to switch to user root:

      The default password of user root is Cloud12#$.

      sudo su root

    3. Run the following command to switch to the directory containing EVS disk logs:

      cd /var/log/apicom/taskmgr/dbs

    4. Run the following command to query all logs relating to the task based on JobID:

      grep -n "jobId" * | less

    5. If the obtained log information is too much for viewing, use query composition to query precise information. An example is provided to query the log information of one specific minute:

      grep -n "jobId" * | grep "2018-04-10 12:07" | less

  5. Determine the cause of the exception based on the additional information queried in 3.

    If Operation is retypeVolume, the disk type fails to be changed. In this case, locate the fault based on the error phase.

    • If ErrorPhase is Monitored a Failed VolumeType Retyping of an EVS Disk, check whether the error information contains the following information:
      • If retype_volume: No Valid host was found. No weighed hosts available is displayed, the cinder cannot find proper backend storage when scheduling backend storage. Perform the following operations to locate the fault:
        • On the Service OM page, check whether the backend storage in volume_type has sufficient virtual and physical capacity. If the backend storage capacity is insufficient, expand the storage pool or add a new storage pool by following the instructions in Capacity Expansion for Service Storage (SAN and FusionStorage Block) in HUAWEI CLOUD Stack 6.5.0 Capacity Expansion Guide.
      • If the error information does not contain the preceding information, locate the fault by referring to Troubleshooting Guide for Typical Cinder Problems. If the problem persists, provide the volume ID and last occurrence time to FusionSphere OpenStack Cinder O&M personnel to locate and rectify the fault.

    If the additional information contains ClientException, it indicates that the retype request fails to be delivered. Locate the fault by referring to Troubleshooting Guide for Typical Cinder Problems and provide the disk ID to the FusionSphere OpenStack Cinder O&M personnel to locate and rectify the fault.

  6. After the problem is resolved, contact the user to change the disk type again.

Related Information


Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 34021

Downloads: 31

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next