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

FusionCloud 6.3.1.1 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 Scheduling Failures

Pod Scheduling Failures

Symptom

The following are the main symptoms of pod scheduling failures:

  1. A message indicating that a pod is in the Pending state is displayed in the kubectl describe pod field.
  2. The values of IP and Node of the pod in the kubectl describe pod field are both empty.

Possible Causes

  • The nodeSelector field of the pod does not match the label of the node.
  • The node has already had an anti-affinity pod.
  • The disk space of the node is fully occupied.

Troubleshooting Method

  1. Check whether the nodeSelector field of the pod matches the label of the node.

    Use PuTTY to log in to the node where the target pod locates as user paas.

    Run the following command to query the nodeSelector field of the pod:

    kubectl -n manage get pod cse-bus-7tjkm -o yaml | grep -C 2 "nodeSelector"

    Run the following command (containing the -l parameter and values of Key and Value of the label. Multiple key–value pairs can be separated by semicolons (;)) to check the node that meets the nodeSelector field configuration:

    kubectl get node -l servergroup.ies.com/Global-Bus=Global-Bus -n ies

    If there are not enough nodes to meet the nodeSelector field of the pod, check the nodes to be labeled and run the kubectl label node $NODE_NAME key1=value1 command to label the node.

    For example, run the kubectl label node 10.8.113.110 servergroup.ies.com/Global-Bus=Global-Bus -n ies command to add a label whose Key is set to servergroup.ies.com/Global-Bus and Value is set to Global-Bus to the 10.8.113.110 node.

  2. Check whether an anti-affinity pod has been deployed on the node.

    Run the following command to check the definition of the anti-affinity pod:

    kubectl -n ies get pod $POD_NAME -o yaml

    POD_NAME: indicates the name of the pod to be checked.

    Run the following command to check whether cse-service-center pod is deployed on the node:

    kubectl -n ies get pod -owide | grep cse-service-center

  3. Check whether the disk space of the node is fully occupied.

    Run the df -h/opt command as the root user to check whether the disk usage of the node where the pod to be deployed reaches 100%.

    If yes, contact technical support for assistance.

Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 23311

Downloads: 37

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