Bug 1903165

Summary: Improve Canary Status Condition handling for e2e tests
Product: OpenShift Container Platform Reporter: Stephen Greene <sgreene>
Component: RoutingAssignee: Stephen Greene <sgreene>
Status: CLOSED ERRATA QA Contact: Hongan Li <hongli>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.7CC: aos-bugs
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:36: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:

Description Stephen Greene 2020-12-01 14:29:43 UTC
See https://github.com/openshift/cluster-ingress-operator/pull/493/files#r533010135.

Once #493 merges, follow up with Miciah's suggestion to simplify the canary status condition checks for the default ingress controller. The current approach works, but is slightly hacky and not ideal, and may be bug prone.

Comment 1 Stephen Greene 2020-12-03 14:54:50 UTC
Working on this. Should have fix in soon.

Comment 4 Hongan Li 2020-12-14 09:49:51 UTC
moving to verified and didn't see issues in e2e tests.

Comment 7 errata-xmlrpc 2021-02-24 15:36: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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633