Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1740387

Summary: Console sync error reason codes are too vague
Product: OpenShift Container Platform Reporter: Samuel Padgett <spadgett>
Component: Management ConsoleAssignee: bpeterse
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: 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
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`

Comment 3 bpeterse 2019-08-28 18:06:43 UTC
Replacing:
- https://github.com/openshift/console-operator/pull/273 (closed)
with:
- https://github.com/openshift/console-operator/pull/274

which finishes out this issue.

Comment 4 shahan 2019-09-10 03:29:16 UTC
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

Comment 5 errata-xmlrpc 2019-10-16 06:35:39 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, 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