Bug 1982973

Summary: RHEL node stuck in Scheduling disabled state after upgrade from 4.5/4.6 to 4.6.38 and later version (with proxy)
Product: OpenShift Container Platform Reporter: jima
Component: InstallerAssignee: aos-install
Installer sub component: openshift-ansible QA Contact: Gaoyun Pei <gpei>
Status: CLOSED DUPLICATE Docs Contact:
Severity: urgent    
Priority: high CC: bleanhar, deparker, gpei, jerzhang, jhou, jialiu, lwan, minmli, rphillips, rteague, schoudha, skumari, smilner, tsze, weinliu, wking, wsun, yanyang
Version: 4.6Keywords: Reopened
Target Milestone: ---   
Target Release: 4.6.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1975907 Environment:
Last Closed: 2021-08-24 19:10:11 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: 1975907, 1984449    
Bug Blocks:    

Comment 1 Scott Dodson 2021-07-19 14:01:45 UTC
The 4.8.z bug was marked blocker- and we've been unable to reproduce within engineering so similarly marking this blocker-. We must have access to an environment to reproduce this.

Comment 3 Russell Teague 2021-08-02 18:16:22 UTC
This issue could be resolved by a recent fix.  Please test again.  See https://bugzilla.redhat.com/show_bug.cgi?id=1975907#c59

Comment 4 jima 2021-08-03 07:44:11 UTC
From https://bugzilla.redhat.com/show_bug.cgi?id=1975907#c59, seems issue is only fixed in 4.9.
will test once backport bug #1988427 on 4.6 has been fixed.

Comment 5 W. Trevor King 2021-08-18 21:58:14 UTC
Only one bug in the series UpgradeBlocker, and the 4.9.0 bug 1975907 already has it an impact-statement request [1].

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1975907#c61

Comment 6 Russell Teague 2021-08-24 17:57:55 UTC
Waiting for a backport to 4.6 of https://bugzilla.redhat.com/show_bug.cgi?id=1984449.

Comment 7 Scott Dodson 2021-08-24 19:10:11 UTC

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