Bug 1826291

Summary: CLUSTER_VERSION flag never gets resolved if the first try fails
Product: OpenShift Container Platform Reporter: Rastislav Wagner <rawagner>
Component: Management ConsoleAssignee: Rastislav Wagner <rawagner>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, hasha, jokerman, spadgett
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Typo caused that an incorrect flag detection is retried if CLUSTER_VERSION resolution fails with 401 or 500 code Consequence: CLUSTER_VERSION flag is never resolved Fix: fix the typo Result: CLUSTER_VERSION flag is retried again if 401 or 500 code occurs
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:29:34 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 Rastislav Wagner 2020-04-21 11:30:59 UTC
CLUSTER_VERSION flag error handling is broken - instead of retrying to resolve the flag again, we try to resolve OPENSHIFT flag.

Comment 3 shahan 2020-04-23 07:02:47 UTC
There is no any defect issues involved with the commit and verified this bug.

4.5.0-0.ci-2020-04-22-212726

Comment 4 Rastislav Wagner 2020-05-11 09:03:09 UTC
moving back to ASSIGNED as I noticed there's still an incorrect function invocation in case of failure

Comment 6 shahan 2020-05-20 03:08:05 UTC
There is no any defect issues involved with the commit and verified this bug.
4.5.0-0.nightly-2020-05-19-041951

Comment 7 errata-xmlrpc 2020-07-13 17:29:34 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:2409