Bug 1740387
| Summary: | Console sync error reason codes are too vague | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Samuel Padgett <spadgett> |
| Component: | Management Console | Assignee: | bpeterse |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.2.0 | CC: | aos-bugs, bparees, hasha, jokerman |
| Target Milestone: | --- | ||
| Target Release: | 4.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-16 06:35:39 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
Samuel Padgett
2019-08-12 19:29:36 UTC
We have several merged PRs addressing this: - https://github.com/openshift/console-operator/pull/269 - https://github.com/openshift/console-operator/pull/271 - https://github.com/openshift/console-operator/pull/272 And one currently outstanding: - https://github.com/openshift/console-operator/pull/273 Replacing: - https://github.com/openshift/console-operator/pull/273 (closed) with: - https://github.com/openshift/console-operator/pull/274 which finishes out this issue. Remove route rule from rolebinding operator-console will got message like that: RouteSyncDegraded FailedCreate routes.route.openshift.io "console" is forbidden: User "system:serviceaccount:openshift-console-operator:console-operator" cannot get resource "routes" in API group "route.openshift.io" in the namespace "openshift-console" 4.2.0-0.nightly-2019-09-09-150607 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-2019:2922 |