When console sync fails, the reason code is always `DegradedSynchronizationError`. This is too vague to know what is wrong from the reason alone. We should look at adding some more specific reason codes for better troubleshooting. A simple fix might be to add the kind into the reason when sync fails for a specific resource, e.g. `DegradedRouteSyncError`
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