Description of problem: Updating the error code pages cm does not cause the router to reload and reflect new changes done for customising error code pages. OpenShift release version: OCP 4.9 Cluster Platform: How reproducible: Always Steps to Reproduce (in detail): 1.edit the custom error pages cm for 404 in openshift-config 2.curl the non-existing route and see if you see the customised page 3. Actual results: Updating the error code pages cm does not cause the router to reload and reflect new changes done for customising error code pages. Expected results: We should watch the custom pages directory for any changes and then reload the router Impact of the problem: 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.
As a workaround rsh into pods and running reload-haproxy in all router pods serves [miheer@localhost aws-ipi-new]$ oc -n openshift-ingress rsh router-default-6647d984d8-q7b58 sh-4.4$ bash -x /var/lib/haproxy/reload-haproxy OR Another workaround is to annotate the route to force a reload.
Code freeze is coming up, so we'll push fixing this BZ to 4.10. Miheer, can you write up a release note about the issue for 4.9?
Sure
Lowering priority to medium as the issue has a workaround. We'll pick this up again in a future sprint.
This issue is stale and closed because it has been a significant time since its creation. If this issue should not be closed please verify the condition still exists on a recent supported release and submit an updated bug.