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-4901 No aos-workflowengine available

ALM-4901 No aos-workflowengine available

Description

This alarm is generated when no aos-workflowengine instance is available in AOS.

Attribute

Alarm ID

Alarm Severity

Alarm Type

4901

Major

Quality of service (QoS) alarm

Parameters

Parameter

Description

Namespace

Specifies the namespace of the service that reports the alarm.

ServiceName

Specifies the name of the service that reports the alarm.

InstanceName

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

Impact on the System

The lifecycle of the AOS stack cannot be executed because no aos-workflowengine instance is available.

System Actions

None

Possible Causes

  • The aos-workflowengine instance status is abnormal.
  • The etcd service is abnormal.
  • The network connection between etcd and aos-cmdbserver is abnormal.
  • The cache of the aos-cmdbserver component fails to be refreshed.

Procedure

  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 obtain the namespace in the management zone:

    kubectl get ns

  4. Run the following command to check whether the status of the pod of aos-workflowengine is normal:

    kubectl get pod -n fst-manage | grep "aos-work"

    Information similar to the following is displayed:

    aos-workflowengine-1870062581-mnprn        1/1       Running   0          14h
    aos-workflowengine-1870062581-rph3k        1/1       Running   0          14h

    If the command output shows that the statuses of all pods of aos-workflowengine are normal (1/1, Running), the pods are normal.

    • If yes, go to 5.
    • If no, go to 7.

  5. Run the following command to check the status of the etcd service:

    kubectl get pod -n fst-manage | grep "etcd-server"

    Information similar to the following is displayed:

    etcd-server-paas-192-168-29-104               1/1       Running   0          1h
    etcd-server-paas-192-168-29-122               1/1       Running   0          1h
    etcd-server-paas-192-168-29-79                1/1       Running   0          1h

    If the statuses of etcd-0, etcd-1, and etcd-2 are normal (1/1, Running) and the number of restart times in the penultimate column is small (less than 10), the pods are normal.

    • If yes, go to 6.
    • If no, go to 7.

  6. Check whether the network connection between aos-cmdbserver and etcd is normal.

    1. Run the following command to query the IP addresses of the etcd servers:

      kubectl get deployment -n fst-manage aos-cmdbserver -oyaml | grep etcd-servers

      Information similar to the following is displayed:

      --etcd-servers=https://192.168.29.104:4001,https://192.168.29.122:4001,https://192.168.29.79:4001
    2. Run the following commands to enter the aos-cmdbserver container:

      kubectl exec -it -n fst-manage `kubectl get pod -n fst-manage | grep aos-cmd | awk '{print $1}' | sed -n '1,1p'` /bin/sh

      '1,1p'` /bin/sh
      sh-4.2$
    3. In the Bash Shell container of 6.b, run the following command for the three server addresses obtained in 6.a:

      curl ServerIP:4001 -kv

      An example command is curl //https://192.168.29.104:4001 -kv.

      If information similar to the following is displayed, the check is passed. Enter exit to exit the container Bash Shell.

      sh-4.2$ curl https://https://192.168.29.104:4001 -kv
      * About to connect() to 192.168.29.104 port 4001 (#0)
      *   Trying 192.168.29.104...
      * Connected to etcd-0.etcd.fst-manage.svc.cluster.local (192.168.29.104) port 4001 (#0)
      • If yes, go to 8.
      • If no, go to 7.

  7. Contact the administrator and check whether the alarm is cleared.

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

  8. Run the following command to restart aos-cmdbserver (the restart takes about 5 minutes):

    kubectl delete pod -n fst-manage `kubectl get pod -n fst-manage | grep aos-cmdb | awk '{print $1}'`

  9. After the restart, run the following command to query the status of the pod:

    kubectl get pod -n fst-manage | grep aos-cmdb

    • If the statuses of all pods are normal (1/1, Running) and the alarm is cleared, no further action is required.
    • If the alarm is not cleared, go to 10.

  10. Contact technical support for assistance.

Alarm Clearing

After the AOS service is working, the system automatically clears the alarm.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 48567

Downloads: 33

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