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.
Working on this. Should have fix in soon.
Expanding this BZ to accommodate other NE-199 cleanups, including https://github.com/openshift/cluster-ingress-operator/pull/493#issuecomment-737430978, https://github.com/openshift/cluster-ingress-operator/pull/476/files#r513779823, and https://github.com/openshift/cluster-ingress-operator/pull/476/files#r513784808.
moving to verified and didn't see issues in e2e tests.
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