Description of problem: Console becomes inaccessible when custom route hostname is the same as the hostname of the default route. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Go to console operator config YAML page 2. Set the custom route hostname to the same hostname as default route uses ``` spec: route: hostname: <same hostname as default route uses> ``` 3. Save changes Actual results: Console becomes inaccessible Expected results: Console should be still accessible and console operator should inform about this duplicate issue with a condition Additional info:
1. Set custom route hostname the same as default console route $ oc edit console.operator cluster ``` spec: route: hostname: <same hostname as default route uses> ``` 2. Check console-operator log, it will show 'custom route hostname is duplicate of default route hostname' E0518 05:43:01.341694 1 status.go:78] CustomRouteSyncDegraded InvalidCustomRouteConfig custom route hostname is duplicate of the default route hostname E0518 05:43:01.341883 1 controller.go:368] console-route-sync--work-queue-key failed with : custom route hostname is duplicate of the default route hostname E0518 05:43:01.358670 1 status.go:78] SyncLoopRefreshDegraded InProgress routes.route.openshift.io "console-custom" not found E0518 05:43:01.358824 1 controller.go:129] {Console Console} failed with: routes.route.openshift.io "console-custom" not found E0518 05:43:03.611828 1 status.go:78] SyncLoopRefreshDegraded InProgress routes.route.openshift.io "console-custom" not found E0518 05:43:03.612103 1 controller.go:129] {Console Console} failed with: routes.route.openshift.io "console-custom" not found E0518 05:43:18.077547 1 status.go:78] CustomRouteSyncDegraded InvalidCustomRouteConfig custom route hostname is duplicate of the default route hostname E0518 05:43:18.077711 1 controller.go:368] console-route-sync--work-queue-key failed with : custom route hostname is duplicate of the default route hostname 3. Visit console route, the default console is still serving correctly Verified on 4.5.0-0.nightly-2020-05-17-220731
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. https://access.redhat.com/errata/RHBA-2020:2409