Bug 1990020

Summary:	updating the error code pages cm does not cause the router to reload and reflect new changes
Product:	OpenShift Container Platform	Reporter:	Miheer Salunke <misalunk>
Component:	Networking	Assignee:	Miheer Salunke <misalunk>
Networking sub component:	router	QA Contact:	Shudi Li <shudili>
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	medium
Priority:	medium	CC:	aos-bugs, hongli, jechen, mfisher, mmasters, shudili
Version:	4.9
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Release Note
Doc Text:	Updating the custom http error code pages configmap does not cause the router to reload and reflect new changes done for customising error code pages. As a workaround rsh into pods and running reload-haproxy in all router pods serves the custom http error code pages [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.	Story Points:	---
Clone Of:
Clones:	2004179 (view as bug list)		Environment:
Last Closed:	2022-11-04 15:42:47 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:
Embargoed:
Bug Depends On:
Bug Blocks:	2004179

Description Miheer Salunke 2021-08-04 15:02:19 UTC

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.

Comment 1 Miheer Salunke 2021-08-04 15:50:56 UTC

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.

Comment 2 Miciah Dashiel Butler Masters 2021-08-31 16:17:07 UTC

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?

Comment 3 Miheer Salunke 2021-09-06 02:17:14 UTC

Sure

Comment 4 Miciah Dashiel Butler Masters 2022-03-31 16:31:29 UTC

Lowering priority to medium as the issue has a workaround.  We'll pick this up again in a future sprint.

Comment 5 mfisher 2022-11-04 15:42:47 UTC

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.