Bug 1834222
| Summary: | Check for custom console route hostname not to be the same as the default route | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jakub Hadvig <jhadvig> |
| Component: | Management Console | Assignee: | Jakub Hadvig <jhadvig> |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.5 | CC: | aos-bugs, jokerman, yapei |
| Target Milestone: | --- | ||
| Target Release: | 4.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: User can point the customURL to the same host as the defaultURL of the console.
Consequence: Console becomes inaccessible when custom route hostname is the same as the hostname of the default route.
Fix: Console operator checks for the duplicate URL.
Result: Console is still accessible and console operator should inform about this duplicate issue with a condition
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-07-13 17:37:10 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: | |||
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 |
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: