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-92 Failed to Update LB

ALM-92 Failed to Update LB

Description

This alarm is reported when the load balancer bound to a service fails to be updated.

Attribute

Alarm ID

Alarm Severity

Alarm Type

92

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

The ELB cannot be accessed.

System Actions

The service keeps updating the load balancer.

Possible Causes

  • The network is abnormal.
  • The ELB works unexpectedly.

Procedure

  1. Obtain the podname and namespace from the Location Info field 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 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 the kubelet log and analyze the cause based on the log:

    kubectl describe pod podname -n namespace

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

    You can find the SVC from the Location Info field in the alarm information.

  5. Run the following command to check whether the ELB cannot be accessed due to network faults:

    ping ELBIP

    ELBIP is the VIP of the ELB LVS node.
    • Yes: Go to 6.
    • No: Go to 9.

  6. Contact the network administrator to restore the network. Then check whether the alarm is cleared.

    • Yes: No further action is required.
    • No: Go to 7.

  7. Run the following command to check whether the ELB works unexpectedly:

    curl ELBIP:8443

    ELBIP is the VIP of the ELB LVS node.
    • Yes: Go to 8.
    • No: Go to 9.

  8. Contact ELB personnel to restore the ELB and then check whether the alarm is cleared.

    • Yes: No further action is required.
    • 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

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 34791

Downloads: 31

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