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-1316002 Hot Patch Is Abnormal

ALM-1316002 Hot Patch Is Abnormal


This alarm is generated when an installed hot patch fails to take effect.


Alarm ID

Alarm Severity

Auto Clear







Fault Location Info

host_id: specifies the ID of the host 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.
  • ErrorInfo: provides error information related to the alarm.

Impact on the System

If the hot patch does not take effect, the running services are not affected. However, the hot patch is usually used to resolve security vulnerabilities. If the hot patch does not take effect, the corresponding security vulnerability is not fixed.

Possible Causes

The CPU usage of the host is excessively high during the installation of the hot patch.


Query the alarm information. If the configuration file is inconsistent, that is, "the patch configuration is inconsistent" is displayed, go to 11.

If the hot patch is abnormal, that is, "hotpatch status is abnormal" is displayed, perform the following steps:

  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.

  1. Check whether the ALM-6018 Host CPU Usage Exceeds the Threshold and ALM-6033 I layer CPU Usage Exceeds the Threshold alarms exist. If yes, the CPU usage of the current node is too high. Clear the alarms according to the corresponding alarm handling procedure, and then go to 7.
  2. Go to the /opt/hotpatch/UVP patch management directory.
  3. Run the following command to access the directory that contains the abnormal patch:

    cd Abnormal patch directory


    Each hot patch has its own directory. For example, if "hostos_2018101107098" is displayed, go to the /opt/hotpatch/UVP/hostos_2018101107098 directory.

  4. Run the following command to install the hot patch:

    sh install

  5. Run the following command to query the status of the hot patch:

    sh query

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

    echo $?

    • If 0 is returned, go to 11.
    • If the return value is not 0, go to 12.

  6. 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 12.

  7. Contact technical support for assistance.
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 46677

Downloads: 33

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