Bug 2265109

Summary:	NooBaaNamespaceBucketErrorState and NooBaaNamespaceResourceErrorState are 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 Gateway	Assignee:	Liran Mauda <lmauda>
Status:	CLOSED ERRATA	QA Contact:	Filip Balák <fbalak>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.15	CC:	ebenahar, lmauda, nbecker, odf-bz-bot
Target Milestone:	---	Keywords:	Regression
Target Release:	ODF 4.15.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.15.0-150	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-03-19 15:32:54 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 Filip Balák 2024-02-20 13:05:31 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, alerts NooBaaNamespaceBucketErrorState and NooBaaNamespaceResourceErrorState are not triggered.

This was found via automated test test_noobaa_ns_bucket.
Jenkins test run with logs: https://ocs4-jenkins-csb-odf-qe.apps.ocp-c1.prod.psi.redhat.com/job/qe-deploy-ocs-cluster-prod/10581

Version of all relevant components (if applicable):
OCS 4.15.0-144

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

No

Is there any workaround available to the best of your knowledge?

No

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

Can this issue reproduce from the UI?

yes

If this is a regression, please provide more details to justify this:
issue will be logged 2nd time, after the bz 1986444 and bz 2184375

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

(issue reproduced manually)

Actual results:
Alerts NooBaaNamespaceBucketErrorState and NooBaaNamespaceResourceErrorState are not present.

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

Comment 11 Filip Balák 2024-03-04 13:22:13 UTC

NooBaaNamespaceBucketErrorState and NooBaaNamespaceResourceErrorState are triggered correctly. --> VERIFIED

Tested with:
ocs 4.15.0-155

Comment 12 errata-xmlrpc 2024-03-19 15:32:54 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 (Important: Red Hat OpenShift Data Foundation 4.15.0 security, enhancement, & 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-2024:1383