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).
ALM-70106 VM HA Stuck in the Intermediate State

ALM-70106 VM HA Stuck in the Intermediate State


This alarm is generated when a migrated VM is stuck in the intermediate state for a long time (more than two hours by default) and may not recover by itself.


Alarm ID

Alarm Severity

Auto Clear



The value is determined by the instance_rebuild_timeout_clear configuration item of nova-api. The default value is True, indicating that the alarm can be automatically cleared.




Fault Location Info

  • instance_id: specifies the ID of the VM for which the alarm is generated.
  • tenant_id: specifies the tenant of the VM for which the alarm is generated.

Additional Info

  • availability_zone: specifies the name of the AZ where the VM for which the alarm is generated is located.
  • instance_name: specifies the name of the VM for which the alarm is generated.
  • hostname: specifies the name of the host accommodating VM for which the alarm is generated.
  • host_id: specifies the ID of the host accommodating the VM for which the alarm is generated.

Impact on the System

The VM cannot be automatically restored.

Possible Causes

  • Packets of the RabbitMQ service are lost.
  • The host management network is faulty.
  • The nova-compute service is restarted.
  • The configured timeout duration of the HA intermediate state is too short.


  1. Use PuTTY to log in to the first FusionSphere OpenStack node through the IP address of the External OM plane.

    The default user name is fsp. The default password is Huawei@CLOUD8.

    The system supports both password and public-private key pair for identity authentication. If the public-private key pair is used for login authentication, see detailed operations in Using PuTTY to Log In to a Node in Key Pair Authentication Mode.

    To obtain the IP address of the External OM plane, search for the required parameter on the Tool-generated IP Parameters sheet of the xxx_export_all.xlsm file exported from HUAWEI CLOUD Stack Deploy during software installation. The parameter names in different scenarios are as follows:
    • Region Type I scenario:

      Cascading system: Cascading-ExternalOM-Reverse-Proxy

      Cascaded system: Cascaded-ExternalOM-Reverse-Proxy

    • Region Type II and Region Type III scenarios: ExternalOM-Reverse-Proxy

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

    su - root

    The default password of user root is Huawei@CLOUD8!.

  3. Run the following command to disable user logout upon system timeout:


  4. Run the following command to import environment variables:

    source set_env

    Information similar to the following is displayed:

      please choose environment variable which you want to import: 
      (1) openstack environment variable (keystone v3) 
      (2) cps environment variable 
      (3) openstack environment variable legacy (keystone v2) 
      (4) openstack environment variable of cloud_admin (keystone v3) 
      please choose:[1|2|3|4] 

  5. Enter 1 to enable Keystone V3 authentication and enter the password of OS_USERNAME as prompted.

    Default account format: DCname_admin; default password: FusionSphere123.

  6. Run the nova show VM ID | grep task_state command to check whether the VM task status is rebuilding, rebuild_block_device_mapping, rebuild_spawning, or rescheduling.

    • If yes, go to 7.
    • If no, manually clear the alarm.

  7. Rectify the fault based on section "Stuck VMs."

  8. Check whether the issue is successfully handled.

    • If the alarm is cleared, no further action is required.
    • If the fault persists, go to 9.

  9. Contact technical support for assistance.

Related Information


Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 45714

Downloads: 33

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