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.

bug is similar to #1986444 Closed ERRATA

Version of all relevant components (if applicable):


OC version:
Client Version: 4.12.0-202208031327
Kustomize Version: v4.5.4
Server Version: 4.13.0-0.nightly-2023-04-01-062001
Kubernetes Version: v1.26.2+7195e44

OCS verison:
ocs-operator.v4.13.0-121.stable              OpenShift Container Storage   4.13.0-121.stable              Succeeded

Cluster version
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.13.0-0.nightly-2023-04-01-062001   True        False         2d3h    Cluster version is 4.13.0-0.nightly-2023-04-01-062001

Rook version:
rook: v4.13.0-0.8eff918ef2611ffdedd08f9bceeab8b1423bee38
go: go1.19.6

Ceph version:
ceph version 17.2.5-1342.el9cp (ed07851f2c5b8d3dccadf079402f86a67cb7d3e5) quincy (stable)


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 #1986444

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

(issue reproduced manually)

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:
must-gather logs: https://url.corp.redhat.com/must-gather