Bug 1553213

Summary: Add CRI-O RPM upgrade to node upgrade playbooks in 3.9.z
Product: OpenShift Container Platform Reporter: Scott Dodson <sdodson>
Component: Cluster Version OperatorAssignee: Russell Teague <rteague>
Status: CLOSED ERRATA QA Contact: Johnny Liu <jialiu>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.9.0CC: aos-bugs, jokerman, mmccomas, rteague, smilner, wmeng
Target Milestone: ---   
Target Release: 3.9.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Tasks have been added to the upgrade playbooks to correctly upgrade the cri-o rpms.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-29 14:42:31 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 Dodson 2018-03-08 14:06:49 UTC
We currently do not address CRI-O at all during the upgrade. Need to make sure that CRI-O is updated to the latest version while the node is drained if CRI-O is in use.

Comment 3 Scott Dodson 2018-06-21 13:33:16 UTC
Needs to just backport changes made to 3.10 installer to ensure that crio is updated during upgrades within 3.9.z

Comment 4 Russell Teague 2018-08-17 12:48:47 UTC
Proposed: https://github.com/openshift/openshift-ansible/pull/9646

Comment 6 Gan Huang 2018-08-21 11:38:35 UTC
Tested with openshift-ansible-3.9.41-1.git.0.4c55974.el7.noarch

Upgrade successfully for 3.9.30 to 3.9.41 and cri-o was also upgraded successfully from cri-o-1.9.12-1.gitfa11beb.el7.x86_64 to cri-o-1.9.14-1.git4e220eb.el7.x86_64.

Please attach a valid build.

Comment 7 Gan Huang 2018-08-22 04:57:28 UTC
Per comment 6, move to verified.

Comment 10 errata-xmlrpc 2018-08-29 14:42:31 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