BMYPC6003

A node is not ready or unscheduleable.

Severity

Error

Problem description

It indicates that a node is not ready or unschedulable. Make sure that all nodes are available before you proceed with the upgrade.

Recommended actions

Do the following steps to resolve the issue:
  1. Check whether the node is placed in a maintenance mode for a planned work. In this case, bring the node out of the maintenance mode after the planned work is complete.
  2. If a machine configuration roll out is in progress, then wait for the roll out to complete and the node to return to a ready state.
  3. If the node is in a Notready state for more than 30 minutes, then it might be an error with the node in the joining cluster. Do the following steps to resolve issues that are related to the joining cluster:
    1. Run the following command to check for the pending CSRs.
      oc get csr|grep -i pending
    2. If you find any pending CSRs, then run the following command to approve them.
      oc get csr -o go-template='{{range .items}}{{if not .status}}{{.metadata.name}}{{"\n"}}{{end}}{{end}}' | xargs oc adm certificate approve
    3. If you do not find any pending CSRs, then restart the node.
    4. Connect to the node by using the core OS private SSH key and run the following command.
      ip a
    5. Recover the node during the following scenarios:
      • IPv4 address assigned to the bond0 interface
      • br-ex interface not created

      For steps to recover the node, see Recover node.

    You can continue with the upgrade operation after the node is in a Ready state.