Member-only story

Openshift 3.x Pod Stuck in Pending Status Due to “no Nodes Available Schedule Pods”

Bryant Jimin Son
2 min readFeb 21, 2020

--

As I have been worked with Openshift, I have been encountered few problems and discovered some solutions along the way. Thus, I want to share them.

One of the rare situations where you encounter is that Pod get stuck in “Pending” status. Thus, when you run:

oc get pods

You will see Pod(s) get stuck in “Pending” STATUS

To troubleshoot, there are multiple ways. But when you do,

oc logs -f POD_NAME

Nothing may show.

Try

oc get events

And you see:

no nodes available to schedule pods

Assuming you have system:admin privilege, try

oc get nodes

This will show if the nodes are Ready or not.

If the nodes are not ready, you have to ssh into the troubled node to see what is the problem.

The typical issue is that docker service is down. You can check by running the command:

systemctl status atomic-openshift-node.service

If that indeed indicates that Docker service is down, you can run:

systemctl status docker.service

Then, if it is down, you can bring it backup by:

systemctl start docker.service

Now, check the status of Docker and Nodes again. They are likely to get fixed.

And your Pod should be “Running” as well.

--

--

Bryant Jimin Son
Bryant Jimin Son

Written by Bryant Jimin Son

A cloud practitioner talking about technology, travels & career tips. But I will sometimes cover financial advises and some random stuffs.

No responses yet