Bug 2077384

Summary: Kuryr: Prometheus when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: NetworkingAssignee: Maysa Macedo <mdemaced>
Networking sub component: kuryr QA Contact: Itay Matza <imatza>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: emacchi, imatza, mbooth, mdulko
Version: 4.6Keywords: Triaged
Target Milestone: ---   
Target Release: 4.10.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-20 07:46:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2070047    
Bug Blocks:    

Comment 1 ShiftStack Bugwatcher 2022-04-22 07:03:31 UTC
Removing the Triaged keyword because:
* the QE automation assessment (flag qe_test_coverage) is missing

Comment 6 Itay Matza 2022-07-12 08:49:58 UTC
Verified with the following steps:

- Installed OCP 4.9.0-0.nightly-2022-06-24-070308 on top of RHOS-16.1-RHEL-8-20220329.n.1 with Kuryr.

- The cluster is up and the Watchdog and AlertmanagerReceiversNotConfigured alerts exist but not the KuryrCNISlow alert:
```
$ curl -sk -H "Authorization: Bearer $token" 'https://prometheus-k8s-openshift-monitoring.apps.ostest.shiftstack.com/api/v1/alerts' | jq '.data.alerts[] | select(.labels.alertname) | .labels.alertname'
"Watchdog"
"CannotRetrieveUpdates"
"AlertmanagerReceiversNotConfigured"
```

- Upgraded successfully to 4.10.22 using the oc upgrade command:
```
$ oc adm upgrade --to-image="registry.ci.openshift.org/ocp/release:4.10.22" --allow-explicit-upgrade --force=true
```

- Make sure the cluster is up.

- Check the alerts, the Watchdog and AlertmanagerReceiversNotConfigured alerts exist, but the KuryrCNISlow is not.

- Keep checking the alerts and make sure the KuryrCNISlow is not raised.

Comment 9 errata-xmlrpc 2022-07-20 07:46:10 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 (OpenShift Container Platform 4.10.23 bug fix 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/RHBA-2022:5568