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-421 Failed to Create Node

ALM-421 Failed to Create Node


This alarm is reported when a node fails to be created.


Alarm ID

Alarm Severity

Alarm Type



Environmental alarm


Parameter Name

Parameter Description


Resource type.


Name of the project to which the resource belongs.


Resource name.


Unique ID of the resource.


Event generation time.


Name of the component that reports an event.


Supplementary information about an event.

Impact on the System

The node fails to be managed, and the node is unavailable.

System Actions


Possible Causes

  • The kube-apiserver service cannot be accessed during node creation.
  • The node template is incorrect.


  1. Obtain the node name and namespaces from the Location Info field in the alarm information.
  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 node log and analyze the cause based on the log:

    kubectl get events -n namespaces | grep node name

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

  5. Check whether the node template is correct.

    kubectl get node node name -n namespaces -oyaml
    • Yes: Go to 7.
    • No: Go to 6.

  6. Correct the node template and then check whether the alarm is cleared.

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

  7. Run the following command separately to check whether the kube-apiserver and etcd services are normal:

    kubectl get pod -n fst-manage | grep kube-apiserver

    kubectl get pod -n fst-manage | grep etcd

    • Yes: Go to 9.
    • No: Go to 8.

  8. Restore the services 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


Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 37279

Downloads: 31

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