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-70108 Faulty VM Directory File

ALM-70108 Faulty VM Directory File

Description

FusionSphere OpenStack periodically (default interval: 5 minutes) checks VM directory files. This alarm is generated if one of the following conditions occur:

  • A host stores a directory file of a VM, but the VM is running stably on another host or has been deleted and does not exist in the UVP system.
  • The VM file is lost on the host accommodating the VM.

Attribute

Alarm ID

Alarm Severity

Auto Clear

70108

Critical

No

Parameters

Name

Meaning

Fault Location Info

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

Additional Info

  • detail_info: provides detailed information about the alarm.
  • hostname: specifies the name of the host for which the alarm is generated.
  • host_id: specifies the ID of the host for which the alarm is generated.

Impact on the System

  • Residual VM files will occupy host disk space. VM creation may fail due to insufficient resources.
  • If the VM file is lost, the VM will not be able to start after it stops.

Possible Causes

  • Services may encounter an exception or processes may restart during the VM deletion process.
  • An error may occur during the VM resize or revert-resize process, or the VM may be deleted.
  • The VM file is deleted by mistake.

Procedure

  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.

    NOTE:
    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:

    TMOUT=0

  1. Import environment variables. For details, see Importing Environment Variables.
  2. Check whether the value of detail_info in Additional Info contains lost files.

    • If yes, go to 6.
    • If no, go to 7.

  3. Run the nova list --all-t | grep VM ID command to check whether the VM exists.

    NOTE:

    Obtain the VM ID from Fault Location Info.

  4. Check whether the VM exists on the alarm host.

    1. In the alarm additional information, obtain the ID of the host where the alarm is generated.
    2. Run the cps host-list | grep Host ID command to obtain the management plane IP address of the host.
    3. Run the su fsp command to switch to user fsp.
    4. Run the ssh fsp@ IP address of the management plane command to switch to the management plane IP address.
    5. Repeat 2 to 4.
    6. Run the runsafe command to enter the secure operation mode:
    7. Run the following command to check whether the VM exists on the alarm host:

      nova_virsh_cmd virsh-list-uuid | grep VM ID

      Check whether the VM information is displayed in the command output.

      • If yes, run the nova show VM ID | grep instance_name command to obtain the VM name in the UVP system (for example, instance-00000070). Run the virsh undefine VM name in the UVP system command to delete the file associated with the VM. Then, go to 14.
      • If no, go to 8.

  5. Run the runsafe command to enter the secure operation mode and run the following command:

    nova show VM ID

    If information similar to the following is displayed, the VM can be queried. In this case, go to 9.

      +--------------------------------------+----------------------------------------------------------+ 
      | Property                             | Value                                                    | 
      +--------------------------------------+----------------------------------------------------------+ 
      | OS-DCF:diskConfig                    | MANUAL                                                   | 
      | OS-EXT-AZ:availability_zone          | az1.dc1                                                  | 
      | OS-EXT-SRV-ATTR:host                 | 253B9B3A-EC06-117B-8567-000000821800                     | 
      

    If message "ERROR (CommandError): No server with a name or ID of 'vm_uuid' exists." is displayed in the command output, go to 12.

  6. In the VM details, check the VM status.

    Check whether the OS-EXT-STS:vm_state field is active, the OS-EXT-STS: power_state field is 1, and the OS-EXT-STS:task_state field is -.

    • If yes, go to 10.
    • If no, contact technical support for assistance.

  7. In the VM details, check whether the host accommodating the VM is the host for which the alarm is generated.

    The OS-EXT-SRV-ATTR:host field specifies the host accommodating the VM.

    • If yes, go to 11.
    • If no, go to 12.

  8. Log in to the host accommodating the VM and run the following command to check whether the VM directory exists:

    ls /opt/HUAWEI/image/instances/VM ID

    Check whether the command output contains message "No such file or directory".

    • If yes, technical support for assistance.
    • If no, go to 12.

  9. Log in to the host for which the alarm is generated and run the following command to check the residual VM file:

    ls /opt/HUAWEI/image/instances/ | grep VM ID

    Check whether the command output is empty.

    • If yes, go to 14.
    • If no, go to 13.

  10. Clear residual VM files named VM ID or VM ID_resize.

    rm -rf /opt/HUAWEI/image/instances/residual_instance_file_name

    residual_instance_file_name indicates the residual VM file name in the command output (files named VM ID or VM ID_resize).

  11. Manually clear the alarm.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 34950

Downloads: 31

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