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.


FusionCloud Troubleshooting Guide 02

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).
Pod in MatchNodeSelector State

Pod in MatchNodeSelector State


Some pods are in MatchNodeSelector state after a power-off and restart.

Possible Causes

After a node restart, kubelet is not connected to kube-api-server.

Troubleshooting Method

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

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

  2. Run the following command to obtain the name of the pods in MatchNodeSelector state:

    kubectl get pods --all-namespaces | grep MatchNodeSelector

  3. Run the following command to delete the pods in MatchNodeSelector state:

    kubectl delete pod --all-namespaces podname

    podname indicates the pod names obtained in step 2.

    Run the command in 2 to check whether the pod is in the Running status. If the pod is not in the Running status, contact technical support for assistance.

Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 22582

Downloads: 37

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