Bug 1830102

Summary: 4.4 MachineSet with 4.2 or earlier bootimages fails to scale up because old CRI-O chokes on new CRI-O config
Product: OpenShift Container Platform Reporter: Steve Milner <smilner>
Component: RHCOSAssignee: Micah Abbott <miabbott>
Status: CLOSED ERRATA QA Contact: Mike Fiedler <mifiedle>
Severity: high Docs Contact:
Priority: urgent    
Version: 4.4CC: bbreard, imcleod, jhou, jligon, jupierce, kgarriso, lmohanty, mifiedle, mnguyen, mpatel, nstielau, scuppett, sdodson, walters, wking
Target Milestone: ---Keywords: Upgrades
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1829642
: 1838984 (view as bug list) Environment:
Last Closed: 2020-05-18 13:35:03 UTC Type: ---
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: 1829642    
Bug Blocks: 1838984    

Comment 1 Steve Milner 2020-04-30 22:00:53 UTC
Backport: https://github.com/openshift/machine-config-operator/pull/1707

Comment 4 Mike Fiedler 2020-05-01 20:11:18 UTC
Verified on 4.4.0-0.nightly-2020-05-01-142756
Scaleup works on cluster upgraded 4.2.29->4.3.18-> this nightly

Comment 9 errata-xmlrpc 2020-05-18 13:35:03 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-2020:2133