Closing this for now. None of the customers who have encountered it are on 3.3, so there's no need yet for a 3.3 backport.
This has been merged into ocp and is in OCP v184.108.40.206 or newer.
Sorry, this was incorrectly changed to MODIFIED while the merge was in progress. The merge flaked on some testing and never completed. I've restarted the merge.
Removing from errata since it's not in OCP v220.127.116.11
It has really merged this time!
The openshift version running inside the router pod is the wrong version...
If you look inside the router container of the ose-haproxy-router:v18.104.22.168 (hash:026e8608ddd0) it is running openshift v22.214.171.124 which is before the fix was added.
We apologize for the issues with the v126.96.36.199 images. Those have been fixed in v188.8.131.52-1.
Please test using v184.108.40.206-1 or newer images.
verified in atomic-openshift-220.127.116.11-1.git.0.708db09.el7.x86_64 and the issue has been fixed, no panic error found in logs.
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.