Bug 1986444

Summary: Alert NooBaaNamespaceBucketErrorState is not triggered when namespacestore's target bucket is deleted
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Filip Balák <fbalak>
Component: Multi-Cloud Object GatewayAssignee: Jacky Albo <jalbo>
Status: CLOSED ERRATA QA Contact: Filip Balák <fbalak>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.8CC: ebenahar, etamir, muagarwa, nbecker, ocs-bugs, odf-bz-bot
Target Milestone: ---Keywords: Automation, Regression
Target Release: ODF 4.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1993873 (view as bug list) Environment:
Last Closed: 2021-12-13 17:44:55 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:
Bug Depends On:    
Bug Blocks: 1993873    

Description Filip Balák 2021-07-27 14:45:06 UTC
Description of problem (please be detailed as possible and provide log
snippests):
When NamespaceStore's target bucket is deleted and the NamespaceStore is used in a Namespace bucket, the alert NooBaaNamespaceBucketErrorState is not triggered. In this case, alert NooBaaNamespaceResourceErrorState for namespace resource is triggered so user is notified that NamespaceStore is unhealthy but the alert for bucket is missing.

Version of all relevant components (if applicable):
v4.8.0-456.ci

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
3

Can this issue reproducible?
yes


If this is a regression, please provide more details to justify this:
Alert for bucket was present in OCS 4.7.

Steps to Reproduce:
1. Create a Namespace bucket with one Namespacestore
2. Delete target bucket used by the Namespacestore
3. Check alerts


Actual results:
Alert NooBaaNamespaceBucketErrorState is not present. Alert NooBaaNamespaceResourceErrorState is raised.

Expected results:
If NamespaceStore is unhealthy then bucket that uses the NamespaceStore is unhealthy too and proper alerts are raised.

Additional info:

Comment 8 Filip Balák 2021-08-24 11:37:50 UTC
The alert is triggered correctly. --> VERIFIED

Tested with:
OCP 4.8.0-0.nightly-2021-08-23-234834
OCS 4.9.0-105.ci

Comment 13 errata-xmlrpc 2021-12-13 17:44:55 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: Red Hat OpenShift Data Foundation 4.9.0 enhancement, security, and 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/RHSA-2021:5086