IBM Support

FailedScheduling for regpod-checking in VA node

Troubleshooting


Problem

In your ICP cluster, the regpod-checking pod is not able to start.

Symptom

Checking output from: kubectl describe pod regpod-checking
you get following:
Name: regpod-checking
Namespace: kube-system
Priority: 0
PriorityClassName: <none>
Node: <none>
Labels: <none>
...
Status: Pending
....
Node-Selectors:    beta.kubernetes.io/arch=amd64
                kubernetes.io/hostname=<FULLY-QUALIFIED-HOSTNAME>
                va=true
Tolerations:    dedicated:NoSchedule
                node.kubernetes.io/not-ready:NoExecute for 300s
                node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 40s (x14 over 9m29s) default-scheduler 0/9 nodes are available: 9 node(s) didn't match node selector.
You can note a couple of things above:
1) FailedScheduling event is reported due to node selector not matching
2) Under Node-Selectors, your VA hostname is fully qualified.

Document Location

Worldwide

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBS6K","label":"IBM Cloud Private"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
07 January 2020

UID

ibm11168660