Bug 1564821

Summary:	When doing a CRI-O based install there is no crictl command
Product:	OpenShift Container Platform	Reporter:	Scott McCarty <smccarty>
Component:	Containers	Assignee:	Jhon Honce <jhonce>
Status:	CLOSED NOTABUG	QA Contact:	DeShuai Ma <dma>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.9.0	CC:	aos-bugs, decarr, dmoessne, jokerman, mmccomas, wmeng
Target Milestone:	---
Target Release:	---
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:	2018-04-27 21:32:50 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 Scott McCarty 2018-04-08 02:58:37 UTC

Description of problem:


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


How reproducible:
100%


Steps to Reproduce:
1. yum install cri-o
2. rpm -ql cri-o: https://pastebin.com/hg4J2PSZ
3. No crictl command, so you can't verify containers are running on a node, you have to trust that they are running in CRI-O, by doing a "docker ps" and verifying that nothing is running in docker: BAD.

Actual results:
No command to verify containers running

Expected results:
Would be really nice to have similar functionality to docker


Additional info:

Comment 1 Scott McCarty 2018-04-08 02:59:45 UTC

Also, I tried building crictl from scratch/upstream code and it fails to connect to the CRI-O/CRI that is installed. It appears to be a version mismatch, but I haven't had a chance to troubleshoot it further yet...

Comment 2 Derek Carr 2018-04-27 21:32:50 UTC

crctl is not yet GA upstream.  we plan to target delivery of it in 3.11.