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-38011 IAMProxy Unavailable

ALM-38011 IAMProxy Unavailable

Description

This alarm is reported when IAMProxy fails to be connected.

Attribute

Alarm ID

Alarm Severity

Alarm Type

38011

Major

Equipment alarm

Parameters

Parameter Name

Parameter Description

SrvAddr

Indicates the access address that reports the alarm.

Namespace

Indicates the namespace of the service that reports the alarm.

ServiceName

Indicates the name of the service that reports the alarm.

InstanceName

Indicates the name of the service instance that reports the alarm.

Impact on the System

The IAMProxy functions are abnormal, and the interfaces between services and IAMProxy are unavailable.

System Actions

None

Possible Causes

  • IAMProxy is unavailable.
  • The IAMProxy node breaks down.
  • The network malfunctions.

Procedure

  1. Query the location and additional information of the alarm service.
  2. Check the iam-proxy pod status.

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

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

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

      su - root

      Default password: QAZ2wsx@123!

    3. Run the following command to check whether the iam-proxy pod status is normal:

      kubectl get pod -n fst-manage -owide | grep iam-proxy

      iam-proxy-3373803100-215w3   1/1       Running   6   4h    172.16.3.23       manage-cluster1-bad57fdd-7jpr7
      iam-proxy-3373803100-vg51w   1/1       Running   6   4h    172.16.4.20       manage-cluster1-bad57fdd-71jp8

      The first column indicates the pod instance name, and the third column indicates the pod status.

      If the iam-proxy pod is in Running state, the iam-proxy pod is normal.

      • If no pod is found, iam-proxy is not installed or is uninstalled. Contact the environment installation personnel to rectify the fault, and then check whether the alarm is cleared.
      • If the pod is found, and the pod status is Running, go to 3.
      • If the pod status is CrashLoopBackOff, go to 4.

  3. Run the following commands to check whether the network connection is normal:

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

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

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

      su - root

      Default password: QAZ2wsx@123!

    3. Run the following command to access the container where the alarm is reported:

      kubectl -n fst-manage exec -ti csc-apiserver-1272234593-5qkg7 sh

      In this command, manage is the value of Namespace, and csc-apiserver-1272234593-5qkg7 is the value of InstanceName.

    4. Run the following command to check whether the network connection is normal:

      curl iam-proxy.fst-manage.svc.cluster.local:30904

      • If the network connection is abnormal, contact the network administrator to rectify the fault.
      • If the network connection is normal, go to 4.

  4. View the run logs of the pod related to iam-proxy.

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

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

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

      su - root

      Default password: QAZ2wsx@123!

    3. Run the following command to query the IP address of any iam-proxy pod:

      kubectl describe podPod instance name-n fst-manage | grep Node

    4. Log in to the node where the pod whose IP address is queried runs as the paas user.
    5. Run the following command to go to the /var/paas/sys/log/iam-proxy directory:

      cd /var/paas/sys/log/iam-proxy

    6. Run the following command to check whether logs at the error level are recorded in the iam-proxy.log file:

      tailf iam-proxy.log | grep error

      • If no error log is recorded, go to 6.
      • If there are recorded error logs, go to 5.

  5. Run the following command to invoke the iam-proxy interface for obtaining tokens:

    curl -k -v https://iam-proxy.fst-manage.svc.cluster.local:30904/v3/auth/tokens -d '{"auth": {"identity": {"methods": ["password"],"password": {"user": {"name": "paasadmin","password": "{Password of the paasadmin user}","domain": {"name": "op_service"}}}},"scope": {"domain": {"name": "op_service"}}}}'

    NOTE:

    In the preceding command, {Password ofthe paasadmin user} indicates the password of the paasadmin user.

    Collect the status code from the returned value.

  6. Collect the location information and 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: 37526

Downloads: 31

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