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-15 Failed to Pull Pod Image

ALM-15 Failed to Pull Pod Image

Description

This alarm is reported when a pod fails to pull images.

Pod: In Kubernetes, pods are the smallest unit of creation, scheduling, and deployment. A pod is a group of relatively tightly coupled containers. Pods are always co-located and run in a shared application context. Containers within a pod share a namespace, IP address, port space, and volume.

Attribute

Alarm ID

Alarm Severity

Alarm Type

15

Major

Environmental alarm

Parameters

Parameter Name

Parameter Description

kind

Resource type.

namespace

Name of the project to which the resource belongs.

name

Resource name.

uid

Unique ID of the resource.

OriginalEventTime

Event generation time.

EventSource

Name of the component that reports an event.

EventMessage

Supplementary information about an event.

Impact on the System

Components or applications become abnormal.

System Actions

The pod keeps pulling images.

Possible Causes

  • The configured image path is incorrect.
  • The image repository does not exist.
  • The software repository is inaccessible.

Procedure

  1. Obtain the name of the pod that fails to be created.

    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, https://oc.type.com:31943.
        • 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. Based on alarm parameters, check whether images keep failing to be pulled due to incorrect image name (An image name should consist of a remote image address and version.).To obtain the image pulling address, log in to the console and choose Marketplace > Software Center > Image Repository.

    • If it is due to incorrect image name, go to5.
    • If it is not due to incorrect image name, go to 6.

  5. Modify the deployment file mapping the pod. Correct the image name. Then, check whether the alarm is cleared. Perform the following steps:

    1. Run the following command to obtain the name of deployment mapping the pod:

      kubectl get pod podname -n namespace

      In the preceding command, podname is the instance name obtained in 1, and namespace is the namespace obtained in 1.

      The name of deployment is displayed as shown in the red box in the following figure.

    2. Run the following command to change the image pulling address in the deployment file:

      kubectl edit deployment deploymentname -n namespace

      In the preceding command, deploymentname is the deployment name obtained in 5.a, and namespace is the namespace obtained in 1.

      The changed contents are shown in the following figure.

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

  6. Run the curl -k -v 10.120.174.85:20202 (10.120.174.85 indicates the image pulling address shown in 4) command on the node where the pod runs to check whether the remote image repository can be accessed.

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

  7. Restore the image repository. Then, check whether the image exists.

    • If it exists, no further action is required.
    • If it does not exist, go to 8.

  8. Choose Marketplace > Software Center > Image Repository. Upload an image on the My Images tab page. Then, check whether the alarm is cleared.

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

  9. Contact technical support for assistance.

Alarm Clearing

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

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 36807

Downloads: 31

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