Description of problem: Backport https://github.com/openshift/cluster-ingress-operator/pull/577 to Openshift 4.6 and 4.7 as this problem resides in these supported releases also. OpenShift release version: 4.6 and 4.7 Cluster Platform: How reproducible: Steps to Reproduce (in detail): 1. 2. 3. Actual results: Expected results: Impact of the problem: This problem was reported by a customer in Openshift 4.6. Can this be back ported to 4.6? Additional info: ** Please do not disregard the report template; filling the template out as much as possible will allow us to help you. Please consider attaching a must-gather archive (via `oc adm must-gather`). Please review must-gather contents for sensitive information before attaching any must-gathers to a bugzilla report. You may also mark the bug private if you wish.
We'll need to backport to 4.7.z and then to 4.6.z. I've begun the 4.7.z backport, but it will need to wait for the original fix to ship in 4.8.0.
The 4.7.z backport is complete. I'll work on the 4.6.z backport this sprint.
We never got the 4.6.z backport done. However, the issue is fixed in the latest 4 major releases of OpenShift (4.10, 4.9, 4.8, and 4.7), and we usually don't backport changes to earlier OpenShift releases except in the case of critical issues. This issue does not appear to be causing an upgrade failure, production outage, or other critical issue, so I am closing the 4.6.z BZ; please upgrade to a newer release to get the fix for the issue.