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-16 Image Lost

ALM-16 Image Lost


This alarm is reported when the image pulling policy is Never and there are no images on the node.


Alarm ID

Alarm Severity

Alarm Type



Environmental alarm


Parameter Name

Parameter Description


Resource type.


Name of the project to which the resource belongs.


Resource name.


Unique ID of the resource.


Event generation time.


Name of the component that reports an event.


Supplementary information about an event.

Impact on the System

The application cannot be created successfully. As a result, related services may be unavailable.

System Actions

The system keeps checking whether the corresponding image exists.

Possible Causes

The image pulling policy is Never and there are no images on the node.


  1. Obtain the value of podname and namespace from the location information in the alarm.

    1. Use a browser to log in to the FusionStage OM zone console.
      1. Log in to ManageOne Maintenance Portal.
        • Login address: https://Address for accessing the homepage of ManageOne Maintenance Portal:31943, for example,
        • The default username is admin, and the default password is Huawei12#$.
      2. On the O&M Maps page, click the FusionStage link under Quick Links to go to the FusionStage OM zone console.
    2. Choose Application Operations > Application Operations from the main menu.
    3. In the navigation pane on the left, choose Alarm Center > Alarm List and query the alarm by setting query criteria.
    4. Click to expand the alarm information. Record the values of name and namespace in Location Info, that is, podname and namespace.

  2. Use PuTTY to log in to the manage_lb1_ip node.

    The default username is paas, and the default password is QAZ2wsx@123!.

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

    su - root

    Default password: QAZ2wsx@123!

  4. Run the following command to check whether the image pulling policy is set to Never:

    kubectl get pod podname -n namespace -oyaml | grep imagePullPolicy

    Podname and namespace were obtained from 1.

    • If the repository can be accessed, go to 9.
    • If the repository cannot be accessed, go to 5.

  5. Run the following command to view the image pulling address and image name:

    kubectl get pod podname -n namespace -oyaml | grep image

    Information similar to the following is displayed:


    The image pull address is and the image name is

  6. Run the following command to obtain the IP address of the node on which the pod runs:

    kubectl get pod podname -n namespace -oyaml | grep -i hostip

    Log in to the node via SSH.

  7. Run the following command to check if the image corresponding to the app exists.

    sudo docker images | grep imageName

    ImageName is the image name obtained in 5.
    • If the image exists, go to 9.
    • If the image does not exists, go to8.

  8. Run the following command to import the corresponding image. Then, check whether the alarm is cleared.

    sudo docker pull imageAddress

    ImageAddress is the image pull address obtained in 5.
    • If yes, no further action is required.
    • If no, go to 9.

  9. Contact technical support for assistance.

Alarm Clearing

This alarm will be automatically cleared after the fault is rectified.

Related Information


Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 36480

Downloads: 31

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