Bug 1672327 - Restart of Docker daemon on master ends in infinite loop
Summary: Restart of Docker daemon on master ends in infinite loop
Keywords:
Status: CLOSED DUPLICATE of bug 1671861
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Master
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.11.z
Assignee: Michal Fojtik
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-04 15:09 UTC by Radomir Ludva
Modified: 2019-02-18 08:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-18 08:56:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Inventory file for OCP v3.11 (4.95 KB, text/plain)
2019-02-04 15:09 UTC, Radomir Ludva
no flags Details
Inventory of OCP v3.09 (1.21 KB, text/plain)
2019-02-04 15:12 UTC, Radomir Ludva
no flags Details
Logs of OCP 3.9 (7.09 KB, text/plain)
2019-02-04 15:13 UTC, Radomir Ludva
no flags Details

Description Radomir Ludva 2019-02-04 15:09:33 UTC
Created attachment 1526831 [details]
Inventory file for OCP v3.11

Description of problem:
It is not possible to restart docker daemon on a master. 

Version-Release number of selected component (if applicable):
bash-4.2# oc version
oc v3.11.69
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO
bash-4.2# rpm -qa | grep release
redhat-release-server-7.6-4.el7.x86_64


Steps to Reproduce:
1. Make a clean installation of OCP v3.9 or v3.11
2. SSH to master of the cluster 
3. systemctl docker stop
4. systemctl docker start 

Actual results:
After systemctl docker stop; systemctl docker start on master it is waiting for infinite loop. You can see the debug of Docker:

Docker options --debug=true:
Feb 04 09:29:29 jusan-ichi-master.example.com oci-systemd-hook[22890]: systemdhook <debug>: afe916bef2f5: Skipping as container command is /bin/node_exporter, not init or systemd
Feb 04 09:29:29 jusan-ichi-master.example.com dockerd-current[22826]: time="2019-02-04T09:29:29.681770978-05:00" level=warning msg="libcontainerd: client is out of sync, restore was called on a fully synced container (73fca2f1e117c810adc39171104ae87afa3c36d0e641c505bc7b34ee444af768)."
Feb 04 09:29:29 jusan-ichi-master.example.com dockerd-current[22826]: time="2019-02-04T09:29:29.682922235-05:00" level=debug msg="libcontainerd: received past event &types.Event{Type:\"start-container\", Id:\"73fca2f1e117c810adc39171104ae87afa3c36d0e641c505bc7b34ee444af768\", Status:0x0, Pid:\"\", Timestamp:(*timestamp.Timestamp)(0xc420478be0)}"
Feb 04 09:29:29 jusan-ichi-master.example.com oci-umount[22893]: umounthook <debug>: afe916bef2f5: only runs in prestart stage, ignoring
Feb 04 09:29:29 jusan-ichi-master.example.com dockerd-current[22826]: time="2019-02-04T09:29:29.72527685-05:00" level=debug msg="containerd: process exited" id=afe916bef2f51d4bd7558cd87a5b01584fb50ea410b6ba69a8dabdc0ff38fc4c pid=init status=143 systemPid=22102
Feb 04 09:29:29 jusan-ichi-master.example.com dockerd-current[22826]: time="2019-02-04T09:29:29.726705020-05:00" level=warning msg="libcontainerd: client is out of sync, restore was called on a fully synced container (3d4671c85c780a54921b85513823d95f55e91412eca9b602fb267a4bceb03367)."
Feb 04 09:29:29 jusan-ichi-master.example.com dockerd-current[22826]: time="2019-02-04T09:29:29.727720829-05:00" level=debug msg="libcontainerd: received past event &types.Event{Type:\"start-container\", Id:\"3d4671c85c780a54921b85513823d95f55e91412eca9b602fb267a4bceb03367\", Status:0x0, Pid:\"\", Timestamp:(*timestamp.Timestamp)(0xc420479a00)}"
Feb 04 09:29:29 jusan-ichi-master.example.com oci-systemd-hook[22940]: systemdhook <debug>: e21490af6a33: Skipping as container command is /usr/bin/pod, not init or systemd
Feb 04 09:29:29 jusan-ichi-master.example.com oci-umount[22941]: umounthook <debug>: e21490af6a33: only runs in prestart stage, ignoring


Expected results:
It is possible to start/stop docker daemon.

Additional info:
On version OCP v3.9 there is the same issue with the same log.

Comment 1 Radomir Ludva 2019-02-04 15:12:46 UTC
Created attachment 1526832 [details]
Inventory of OCP v3.09

Comment 2 Radomir Ludva 2019-02-04 15:13:57 UTC
Created attachment 1526833 [details]
Logs of OCP 3.9

Comment 6 Radomir Ludva 2019-02-18 08:56:13 UTC

*** This bug has been marked as a duplicate of bug 1671861 ***


Note You need to log in before you can comment on or make changes to this bug.