Bug 2117646

Summary:	Changing `spec.host` field on any of routes in the openshift-console namespace wont trigger sync loop
Product:	OpenShift Container Platform	Reporter:	Jakub Hadvig <jhadvig>
Component:	Management Console	Assignee:	Jakub Hadvig <jhadvig>
Status:	CLOSED ERRATA	QA Contact:	Yanping Zhang <yanpzhan>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.12	CC:	yapei
Target Milestone:	---
Target Release:	4.12.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-17 19:54:46 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:

Description Jakub Hadvig 2022-08-11 14:02:05 UTC

Description of problem:
Changing `spec.host` field on any of routes in the openshift-console namespace wont trigger sync loop.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Go to either `downloads` or `console` route in the openshift-console namespace. 
2. Edit the `spec.host` field
3.

Actual results:
The route hostname will stay modified

Expected results:
console-operator should undo the changes to the defalut value.

Additional info:

Comment 2 Yanping Zhang 2022-09-06 07:15:42 UTC

Checked on ocp 4.12 cluster with payload 4.12.0-0.nightly-2022-09-05-090751.
Edit the `spec.host` field of console and downloads route in openshift-console namespace, after click "Save", it shows "Info alert:This object has been updated.", click "Reload", the spec.host has been recovered to default value.
The bug is fixed.

Comment 5 errata-xmlrpc 2023-01-17 19:54:46 UTC

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.12.0 bug fix and security 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-2022:7399