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-105 ELB Is Unavailable

ALM-105 ELB Is Unavailable

Description

This alarm is reported when PaaS platform fail to be interconnected with ELB.

Attribute

Alarm ID

Alarm Severity

Alarm Type

105

Major

Environment 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

The unavailable ELB may cause unavailable ELB-related functions in the cluster.

System Actions

The system keeps connecting to ELB.

Possible Causes

The ELB address is unreachable, or the ELB service is unavailable. As a result, ingress-controller fails to obtain information related to ELB instances and listeners from the ELB service, or ingress-controller fails to create ELB instances and listeners.

Procedure

  1. Obtain the name and namespace of the node based on the location information in the alarm information.

    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> Alarm Center > Alarm List to view alarm details.
    3. Choose Location Info > name to obtain the name of the pod that fails to be created.
    4. Obtain the namespace (used in the following contents) where the application that fails to be created resides by viewing the value of namespace in the Location Info field in the alarm details area.

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

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

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

    su - root

    Default password: QAZ2wsx@123!

  2. Run the following commands to obtain the IP address of the node where the pod that fails to be created resides:

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

    kube-system ingress-controller-675679cbc4-wvdrb

    kubectl get pod ingress-controller-675679cbc4-wvdrb -n kube-system-oyaml | grep -i hostip:

    podname indicates the node name obtained in 1, and namespace is the namespace obtained in 1.

    The following information displayed indicates the IP address of the node where the queried pod resides.

      hostIP: 10.118.29.218

  3. Log on to the node where the pod resides and switch to the root user.

    1. Use PuTTY to log in to the node where the pod resides as the paas user.

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

      The node IP address is the IP address obtained in 4.

    2. Run the following command to switch to the root user:

      su - root

  4. Identify the fault cause..

    1. Run the following commands to view the ingress-controller log:

      cd /var/paas/sys/log/kubernetes/

      vi ingress-controller.log

      Press the slash sign (/) to enter "Error doRequest with ELB". Press Enter to view the fault cause and obtain the URL through which nodes cannot communicate with ELB.

    2. Run the curl -k url command to check whether the ELB address is reachable. url indicates the URL obtained in 6.a.
      • If the information "Connection refused" is displayed, go to 8.
      • If information other than "Connection refused" is displayed, go to 7.

  5. Check whether the ELB service is normal.

    • If the ELB service is normal, no further action is required.
    • If the ELB service is abnormal, go to 8.

  6. 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: 36215

Downloads: 31

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