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

Reminder

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

upgrade

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-70102 VM State Error

ALM-70102 VM State Error

Description

This alarm is generated when the VM status keeps ERROR for about four minutes.

Attribute

Alarm ID

Alarm Severity

Auto Clear

70102

Critical

Yes

Parameters

Name

Meaning

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.
  • region_name: specifies the region of the tenant of the VM for which the alarm is generated.

Additional Info

  • availability_zone: specifies the AZ of the VM for which the alarm is generated
  • tenant_name: specifies the tenant of the VM for which the alarm is generated.
  • instance_name: specifies the name of the VM for which the alarm is generated.
  • hostname: specifies the name of the host accommodating the 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

If the high availability (HA) function is enabled on a VM, the error state triggers the VM rescheduling. If the HA function is not enabled on the VM, the VM remains in the error state.

Possible Causes

  • The VM stops exceptionally during running on the host (for example, the VM is abnormally stopped or the process disappears). The management program fails to restore the VM, thereby changing the VM state to error.
  • When the database or the message queue service is unstable, the host and VM need to be restarted. During the restart, the database or message queue may fail to be connected to the VM, thereby changing the VM state to error.
  • When the HA-enabled VM is running, the host accommodating this VM is abnormally powered off or the management network is disconnected. In this case, the VM re-creation fails and VM state becomes error when the HA-enabled VM rescheduling is triggered.
  • After the HA-enabled VM state becomes error (due to the previous reasons for example), the VM cannot be recreated or the recreation process is abnormally interrupted (due to the management program error or the host exception). Then the VM remains in the error state and the rebuilding task status, and the re-creation cannot be triggered again.

Procedure

  1. On Service OM, choose Services > Computing > ECS > Compute Instances to switch to the VM list page and check whether the Power Status is Stopped or Running.

    • If yes, go to 5.
    • If no, go to 2.

  2. On Service OM, choose Services > Centralized O&M > Alarm > Alarm List and check whether Task Status is empty in the VM information.

    • If yes, go to 3.
    • If no, go to 4.

  3. On Service OM, check whether the following alarms exist:

    • ALM-6023 Host Storage Link Failure
    • ALM-6021 Host Network Port Fault
    • ALM-6026 Faulty Fiber Channels on the Host

    If yes, clear the alarms according to the alarm help and then go to 5.

    If no, restart the ceilometer-agent-central service and check whether the alarm is automatically cleared after 5 minutes.

    Run the following commands on the FusionSphere OpenStack background to restart the service:

    cps host-template-instance-operate --service ceilometer ceilometer-agent-central --action stop

    cps host-template-instance-operate --service ceilometer ceilometer-agent-central --action start

    • If the alarm is automatically cleared, no further action is required.
    • If the alarm is not automatically cleared, go to 4.

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

  5. On Service OMchoose Services > Computing > ECS > Compute Instances. On the displayed page, choose More > Close to stop the VM and wait until the status of the VM changes to Stopped. Then, start a VM.

    • If the operation succeeds, no further action is required.
    • If the operation fails, go to 6.

  6. Contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 37733

Downloads: 31

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