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-1316003 Incorrect QEMU Version

ALM-1316003 Incorrect QEMU Version

Description

After the QEMU hot swap patch is installed, this alarm is generated if QEMU of the old version is still used on a VM. This alarm is cleared when all VMs on the host use QEMU of the new version.

Attribute

Alarm ID

Alarm Severity

Auto Clear

1316003

Major

Yes

Parameters

Name

Meaning

Fault Location Info

host_id: specifies the ID of the host for which the alarm is generated.

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

Additional Info

  • Service: specifies the name of the service for which the alarm is generated.
  • MicroService: specifies the name of the microservice for which the alarm is generated.
  • hostname: specifies the name of the host for which the alarm is generated.
  • instance_name: specifies the name of the VM for which the alarm is generated.
  • ErrorInfo: provides error information related to the alarm.

Impact on the System

The QEMU component on a VM has not been replaced with the one with the new version. The QEMU hot swap patch is used to resolve security vulnerabilities. This exception indicates that the corresponding VM security vulnerabilities are not fixed.

Possible Causes

  • The system is abnormal.
  • A device that does not support QEMU hot swap is configured on the VM, for example, a vGPU device.

Procedure

  1. Obtain the VM UUID in the alarm information and locate the host.
  2. 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

  3. 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!.

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

    TMOUT=0

  5. 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] 

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

    Default account format: DCname_admin; default password: FusionSphere123.

  7. Run the following command to perform hot swap on the VM: This command is used to obtain the VM list on the host and perform QEMU hot swap on VMs whose QEMU version is abnormal one by one.

    python /usr/libexec/uvp_hotreplace_upgrade --action=upgradevm | grep -w "Domain"

    • If the hot swap is successful, the following key log is displayed:

      [ INFO ] ... Domain %s do hot replace success

    • Otherwise, the following key log is displayed:

      [ ERROR ] ... Domain %s hot replace fail, reason %s

    NOTE:

    %s indicates the VM name and failure cause.

  8. Run the following command to query the hot swap result:

    python /usr/libexec/uvp_hotreplace_upgrade --action=check_vm_running_at_current_bin 2&>1 > /dev/null

    Run the following command to check the return value of the command:

    echo $?

    • If the return value is 0, the repair is successful. In this case, go to 9.
    • If the returned value is not 0, restart the VM whose QEMU version is abnormal to rectify the fault. Then, go to 9.

    During VM restart, the VM is shut down and then restarted (the new VM will use the QEMU of the new version). This operation will interrupt services on the VM.

  9. Check whether the alarm is automatically cleared after the next check period (12 hours).

    • If yes, no further action is required.
    • If no, go to 10.

  10. Contact technical support for assistance.
Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 49051

Downloads: 33

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