Bug 1890652 - Node stuck in NotReady state during 4.5 to 4.6 upgrade
Summary: Node stuck in NotReady state during 4.5 to 4.6 upgrade
Keywords:
Status: CLOSED DUPLICATE of bug 1887607
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.5
Hardware: Unspecified
OS: Unspecified
low
high
Target Milestone: ---
: 4.7.0
Assignee: aos-install
QA Contact: Gaoyun Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-22 16:34 UTC by Sunil Choudhary
Modified: 2020-10-23 14:09 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-23 14:09:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.