Bug 1948701 - unneeded CCO alert already covered by CVO
Summary: unneeded CCO alert already covered by CVO
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Credential Operator
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.8.0
Assignee: Joel Diaz
QA Contact: wang lin
URL:
Whiteboard:
Depends On:
Blocks: 1948702 1957424
TreeView+ depends on / blocked
 
Reported: 2021-04-12 18:44 UTC by Joel Diaz
Modified: 2021-07-27 22:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Removed functionality
Doc Text:
The cluster-version operator is responsible for reporting if the cloud-credential-operator's deployment is unhealthy; no need for the cloud-credential-operator to handle this directly (resulting in doubling reporting if there's an issue).
Clone Of:
: 1948702 1957424 (view as bug list)
Environment:
Last Closed: 2021-07-27 22:59:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:59:43 UTC

Description Joel Diaz 2021-04-12 18:44:36 UTC 
Description of problem:
CVO already is responsible for alerting on whether its operands are unhealthy. No need for CCO to have its own alert.


Version-Release number of selected component (if applicable):
4.7

How reproducible:
100%

Steps to Reproduce:
1. Put CCO into an unhealthy state.

Actual results:
Witness CVO and CCO alerts reporting the same information.


Expected results:
Only need a single alert.


Additional info:
Comment 2 wang lin 2021-04-13 12:43:48 UTC 
Hi, Joel

I checked the CloudCredentialOperatorDown alert has removed from cco, and when I create a wrong credentialsrequest, co cloud-credential will be degraded, then cvo will show CloudCredentialOperatorDown and ClusterOperatorDegraded alerts.

Before,I through scaling down cco and cvo deployments replicas to 0, cco will show the CloudCredentialOperatorDown alert to reflect the pod is not running. But now, the CloudCredentialOperatorDown alert is owned by cvo, I am not sure if cvo will show CloudCredentialOperatorDown when cco pod crash, because I can't reproduce a cco pod crash scenario. if I only scale down cco deployment replica to 0, cvo will reset it.
Comment 3 wang lin 2021-04-13 12:51:59 UTC 
sorry, I write the wrong content above, when co cloud-credential will be degraded, cvo will show ClusterOperatorDown and ClusterOperatorDegraded alerts.
Comment 4 Joel Diaz 2021-04-13 13:45:23 UTC 
Ok, so it sounds like CVO is handling the alerting instead of CCO also having its own alert.
Comment 5 wang lin 2021-04-14 08:09:43 UTC 
ok, thanks joel.  
verified on 4.8.0-0.nightly-2021-04-09-222447.
Comment 8 errata-xmlrpc 2021-07-27 22:59:27 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), 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/RHSA-2021:2438
Note You need to log in before you can comment on or make changes to this bug.