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


To have a better experience, please upgrade your IE browser.


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-2014 Failed to Connect to the Configuration Center

ALM-2014 Failed to Connect to the Configuration Center


This alarm is generated when cse-governance-service fails to connect to cse-config-center.


Alarm ID

Alarm Severity

Alarm Type



Environmental alarm





Indicates the namespace of the service for which the alarm is generated.


Indicates the name of the service for which the alarm is generated.


Indicates the name of the service instance for which the alarm is reported.


Indicates the IP address of the host where the microservice instance is deployed.

Impact on the System

When the connection to the configuration center fails, some functions of the governance center are unavailable.

Possible Causes

  • A network fault occurs.
  • Domain name resolution fails.
  • The configuration center status is abnormal.


  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. Check whether the network is normal.

    1. Run the required commands to access the pod of the CSE service (for example, cse-governance-service-3753537994-rpmgf) for which the alarm is generated:

      kubectl get pod -n fst-manage | grep cse-governance-service

      kubectl -n fst-manage exec -it cse-governance-service-3753537994-rpmgf sh

    2. Run the required command in the pod to check whether the network is normal:

      curl -kv https://cse-config-center.fst-manage.svc.cluster.local:31103

      The network is normal if information similar to the following is displayed.

  4. Check the configuration center status.

    Log in to the manage_lb1_ip node and run the following command to check the service status.

    kubectl get pod -n fst-manage | grep cse-config-center

    • If the configuration center is abnormal, restart the instance to rectify the fault.

      Restart all the pods of cse-config-center. The following uses the pod of cse-config-center-3081721567-616lj as an example to show how to restart a pod:

      kubectl delete pod -n fst-manage cse-config-center-3081721567-616lj

    • If the configuration center is normal, go to the next step.

  5. Check whether the Domain Name Service (DNS) resolution is normal.

    1. Check whether the /etc/resolv.conf permission and content of the pod are correct.

      If any user can read the /etc/resolv.conf file, the permission is normal.

      • If the /etc/resolv.conf file contains the following information, the file content is normal:
        search fst-manage.svc.cluster.local svc.cluster.local cluster.local
        options ndots:4
    2. If the DNS resolution is normal but the network connection fails, restart the service pod. If the alarm persists, contact IaaS engineers.

      The following uses the pod of cse-governance-service-3753537994-rpmgf as an example to describe how to restart a pod:

      kubectl delete pod -n fst-manage cse-governance-service-3753537994-rpmgf

      After the command is executed, the pod of cse-governance-service-3753537994-rpmgf is deleted and another pod whose name starts with cse-governance-service is generated.

  6. Check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Alarm Clearing

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

Related Information


Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 48988

Downloads: 33

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