Bug 1574660

Summary: [CRI-O] master-restart script uses docker commands when control plane is running on crio
Product: OpenShift Container Platform Reporter: Mike Fiedler <mifiedle>
Component: ContainersAssignee: Mrunal Patel <mpatel>
Status: CLOSED DUPLICATE QA Contact: DeShuai Ma <dma>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.10.0CC: amurdaca, aos-bugs, ccoleman, dwalsh, hongkliu, jokerman, mmccomas, mpatel, wmeng
Target Milestone: ---   
Target Release: 3.10.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-21 09:38:51 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:

Description Mike Fiedler 2018-05-03 19:19:25 UTC 
Description of problem:

The master-restart shim is using docker commands directly.  This does not work when the control plane nodes are running cri-o.   Do we intend these commands for customer consumption?   I see TODOs in the scripts for cri-o but they are currently not implemented.


Version-Release number of selected component (if applicable):  3.10.0-0.32.0


How reproducible: Always


Steps to Reproduce:
1. On a cluster using cri-o as the container run time, master-restart api


Actual results:

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?


Expected results:

Master api restarts
Comment 1 Wang Haoran 2018-05-04 05:18:59 UTC 
Hi, clayton, as you said we will using crictl instead in the master-restart scripts, do you have any plan when this will happen? will it be 3.10?
Comment 3 Antonio Murdaca 2018-05-21 09:38:51 UTC 
This is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1572440

*** This bug has been marked as a duplicate of bug 1572440 ***
Comment 4 Red Hat Bugzilla 2023-09-14 04:27:37 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days