Bug 1890652

Summary: Node stuck in NotReady state during 4.5 to 4.6 upgrade
Product: OpenShift Container Platform Reporter: Sunil Choudhary <schoudha>
Component: InstallerAssignee: aos-install
Installer sub component: openshift-ansible QA Contact: Gaoyun Pei <gpei>
Status: CLOSED DUPLICATE Docs Contact:
Severity: high    
Priority: low CC: bbreard, imcleod, jligon, nstielau, walters, yanyang
Version: 4.5Keywords: UpcomingSprint
Target Milestone: ---   
Target Release: 4.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: 2020-10-23 14:09:04 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:

Comment 2 Colin Walters 2020-10-22 16:48:54 UTC
RHCOS/MCO don't do much with RHEL7, you need openshift-ansible

Comment 3 Russell Teague 2020-10-22 17:25:27 UTC
Please attache verbose Ansible logs.

Was the cluster upgrade to 4.6 complete prior to starting the RHEL7 node upgrades?

Comment 4 Sunil Choudhary 2020-10-23 14:09:04 UTC
The node was stuck during cluster upgrade and openshift ansible was not yet running. Also came across bug https://bugzilla.redhat.com/show_bug.cgi?id=1887607 where currently there is issue with ovn and RHEL nodes.

I will close this one as duplicate of above bug.

*** This bug has been marked as a duplicate of bug 1887607 ***