Bug 1692401

Summary: [starter-us-west-2] Nodes turning NotReady over time - docker stuck in 'activating'
Product: OpenShift Container Platform Reporter: Justin Pierce <jupierce>
Component: ContainersAssignee: Jhon Honce <jhonce>
Status: CLOSED INSUFFICIENT_DATA QA Contact: weiwei jiang <wjiang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: aos-bugs, dwalsh, gblomqui, jfiala, jokerman, mmccomas, mpatel
Target Milestone: ---   
Target Release: 3.11.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-14 21:00:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
unit failed to restart?
none
Other services listings
none
last info from docker service before hang during init none

Comment 3 Justin Pierce 2019-03-26 18:03:20 UTC
Created attachment 1548160 [details]
unit failed to restart?

Last log entry suggest restart was scheduled for "Mar 26 09:18:21" . This status was collected at system time "Mar 26 17:57:15" .

Comment 4 Justin Pierce 2019-03-26 18:13:58 UTC
Created attachment 1548186 [details]
Other services listings

It looks like the docker service has been activating since about the time the atomic-openshift-node stopped restarting (see previous attachment). atomic-openshift-node is probably just waiting on it.

Comment 5 Justin Pierce 2019-03-26 18:19:37 UTC
Created attachment 1548187 [details]
last info from docker service before hang during init

Comment 6 Seth Jennings 2019-03-26 18:23:40 UTC
Yes, the atomic-openshift-node service has an explicit dependency on docker and it does seem to be hanging in its start up somewhere.

Sending to Containers.

Comment 10 Jhon Honce 2020-05-14 21:00:03 UTC
Stale bug