Bug 1614916

Summary:	[3.9] Need to make crio installs rpm installs by default
Product:	OpenShift Container Platform	Reporter:	Scott Dodson <sdodson>
Component:	Installer	Assignee:	Russell Teague <rteague>
Status:	CLOSED ERRATA	QA Contact:	Johnny Liu <jialiu>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.9.0	CC:	aos-bugs, jokerman, mmccomas, rteague, wkulhane
Target Milestone:	---
Target Release:	3.9.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Removed the variable 'openshift_crio_use_rpm' and updated installer tasks to only install cri-o using rpm.	Story Points:	---
Clone Of:
Clones:	1618425 (view as bug list)		Environment:
Last Closed:	2018-08-29 14:42:32 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:
Bug Depends On:
Bug Blocks:	1618425

Description Scott Dodson 2018-08-10 17:35:07 UTC

Description of problem:
In 3.9, if openshift_use_crio=true but openshift_crio_use_rpm is unset a system container based installation is used for CRI-O. This has been found to be problematic and we'd like everyone to install via RPMs.

As such, we should change the default in installation playbooks.
In upgrade playbooks we should check nodes prior to upgrade and if nodes are persent with system container based cri-o we need to refer them to a KCS article that explains the process for transitioning a node to RPM based installation.

ex:
drain node
atomic uninstall cri-o
yum install cri-o
uncordon node

If this process easy to automate we should consider just doing it, if it's not then the subset of customers in this scenario should be small enough that we can coordinate with support.

Comment 2 Russell Teague 2018-08-13 19:06:40 UTC

Proposed: https://github.com/openshift/openshift-ansible/pull/9561

Have not worked out upgrade situation yet.

Comment 3 Scott Dodson 2018-08-15 17:19:38 UTC

*** Bug 1605232 has been marked as a duplicate of this bug. ***

Comment 4 Russell Teague 2018-08-15 19:12:24 UTC

3.10 Upgrade, switch from cri-o system container to RPM:
https://github.com/openshift/openshift-ansible/pull/9615

Comment 5 Russell Teague 2018-08-16 15:30:29 UTC

Moved upgrade portion to a new bug.

Comment 6 Russell Teague 2018-08-16 15:31:23 UTC

Merged to release-3.9: https://github.com/openshift/openshift-ansible/pull/9561

Comment 8 Gan Huang 2018-08-21 06:48:50 UTC

Tested with openshift-ansible-3.9.41-1.git.0.4c55974.el7.noarch.rpm

rpm cri-o could be installed successfully once "openshift_use_crio=true" set only in inventory file.

Please attach a valid build to the errata.

Comment 9 Gan Huang 2018-08-21 08:42:46 UTC

While testing against Atomic Host with "openshift_use_crio=true" set, the installation will be blocked as following:

TASK [container_runtime : Fail if Atomic Host since this is an rpm request] ****
Tuesday 21 August 2018  16:41:06 +0800 (0:00:00.046)       0:00:58.740 ******** 
fatal: [host-xxxx]: FAILED! => {"changed": false, "msg": "Cannot use CRI-O as a package on Atomic Host"}

Comment 10 Gan Huang 2018-08-22 04:56:34 UTC

Per comment 8 and comment 9, move to verified.

Comment 13 errata-xmlrpc 2018-08-29 14:42:32 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/RHBA-2018:2549