DX OI: Pods fail to schedule by docker daemon down or OpenShift console could not access by HTTP ERROR 502

book

Article ID: 186229

calendar_today

Updated On:

Products

DX Operational Intelligence

Issue/Introduction

Many Pods failed to schedule by following message:
0/n nodes are available : n MatchNodeSelector.

or 

You could not access to the OpenShift console GUI by 'HTTP ERROR 502'.

Environment

OpenShift 3.x

Resolution

(1) Check the node status

# oc get nodes

NAME                          STATUS     ROLES            AGE       VERSION

openshift1.local.net   NotReady   compute,master   83d       v1.9.1+a0ce1bc657

openshift2.local.net   Ready      compute          83d       v1.9.1+a0ce1bc657

openshift3.local.net   Ready      compute          83d       v1.9.1+a0ce1bc657



(2) Check the Docker service

# systemctl status docker

●docker.service - Docker Application Container Engine

   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)

  Drop-In: /etc/systemd/system/docker.service.d

           mqcustom.conf

   Active: inactive (dead) since Tue 2020-03-10 15:41:22 JST; 8min ago


(3) Restart the docker service

# systemctl start docker
# systemctl status docker

docker.service - Docker Application Container Engine

   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)

  Drop-In: /etc/systemd/system/docker.service.d

           mqcustom.conf

   Active: active (running) since Fri 2020-01-10 17:00:02 JST; 20min ago

# oc get nodes
NAME                          STATUS    ROLES            AGE       VERSION

openshift1.local.net   Ready     compute,master   83d       v1.9.1+a0ce1bc657

openshift2.local.net   Ready     compute          83d       v1.9.1+a0ce1bc657

openshift3.local.net   Ready     compute          83d       v1.9.1+a0ce1bc657

 

Now all Pods are successfully scheduled.