Bug 1740368 - 35 clusters with unavailable machine config operators
Summary: 35 clusters with unavailable machine config operators
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.3.0
Assignee: Antonio Murdaca
QA Contact: Micah Abbott
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-12 18:26 UTC by Ben Parees
Modified: 2019-11-07 20:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-07 20:46:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Ben Parees 2019-08-12 19:04:47 UTC 
There are a similar number reporting degraded, mostly with "Failed to sync" as the reason.  Possibly related, should be investigated in conjunction.
Comment 2 Antonio Murdaca 2019-08-29 16:28:45 UTC 
The reason for a failure to sync has been enhanced with https://bugzilla.redhat.com/show_bug.cgi?id=1744764 (targets 4.2) - we're working to backport that to 4.1 via https://bugzilla.redhat.com/show_bug.cgi?id=1741065 - meanwhile, we're getting in touch with customers and clusters owners to understand more about what's going on with their clusters (example https://bugzilla.redhat.com/show_bug.cgi?id=1744301)

Given we got an handle on this and we're actively investigating clusters in our telemetry system, I feel moving this bug to 4.3 as it's going to be an ongoing task.
Comment 3 Kirsten Garrison 2019-11-07 20:46:22 UTC 
Closing as we are receiving/investigating individual telemetry reports to investigate (as opposed to using this as an ongoing task) and have backported relevant fixes to 4.1/4.2.

Investigating telemetry is an ongoing task as opposed to a bug.
Note You need to log in before you can comment on or make changes to this bug.