Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1490323

Summary:	No cri-o image
Product:	OpenShift Container Platform	Reporter:	Gan Huang <ghuang>
Component:	Release	Assignee:	Jhon Honce <jhonce>
Status:	CLOSED ERRATA	QA Contact:	Gan Huang <ghuang>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.7.0	CC:	aos-bugs, jhonce, jialiu, jokerman, jupierce, mifiedle, mmccomas, smunilla, xtian
Target Milestone:	---
Target Release:	3.7.0
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:	2017-11-28 22:09:56 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 Gan Huang 2017-09-11 10:48:41 UTC

Description of problem:
There's no cri-o image for ocp-3.7 testing. It's blocking testing cri-o with OCP.

Version-Release number of the following components:


How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Additional info:
It's being tracked in: https://trello.com/c/ndF8GmhS/642-3-cri-o-rhel-build

Comment 4 Justin Pierce 2017-09-20 14:05:35 UTC

I've pushed this image to:
registry.ops.openshift.com/openshift3/cri-o:v1.0.0-1
registry.ops.openshift.com/openshift3/cri-o:v1.0.0
registry.ops.openshift.com/openshift3/cri-o:latest

Comment 7 Justin Pierce 2017-09-26 19:58:26 UTC

There is now a nightly (midnight Eastern time) Jenkins job which pushes whatever cri-o image Version&Release is specified in the distgit Dockerfile to registry.ops and registry.reg-aws.openshift.com.

Until CD is responsible for building this image (instead of just pushing it), this is all we typically provide.

Comment 19 errata-xmlrpc 2017-11-28 22:09:56 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:3188