Bug 1900749

Summary: Namespace Resource reported as Healthy when target bucket deleted
Product: [Red Hat Storage] Red Hat OpenShift Container Storage Reporter: Filip Balák <fbalak>
Component: Multi-Cloud Object GatewayAssignee: Romy Ayalon <rayalon>
Status: CLOSED ERRATA QA Contact: Filip Balák <fbalak>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.6CC: ebenahar, etamir, muagarwa, nbecker, ocs-bugs
Target Milestone: ---Keywords: AutomationBackLog
Target Release: OCS 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.7.0-696.ci Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-19 09:16:24 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 2020-11-23 16:23:14 UTC 
Description of problem (please be detailed as possible and provide log
snippests):
If target bucket used in Namespace resource is removed (on cloud provider side) then the resource is still marked as Healthy in Multi Cloud Object Gateway. It is also possible to create a Namespace bucket using using this Namespace resource and the bucket is also reported as Healthy

Version of all relevant components (if applicable):
ocs-operator.v4.6.0-160.ci


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

Can this issue reproducible?
yes

Can this issue reproduce from the UI?
partially


Steps to Reproduce:
1. Create a Namespace resource with valid target bucket.
2. Delete target bucket from Namespace resource on cloud provider side (e.g. delete the bucket in AWS).
3. Open Multi Cloud Object Gateway console and navigate to Resources.
4. Check status of created resource.
5. Create Namespace bucket by using the resource (use it as both write and read resource or add more resources).
6. Check status of the new bucket.

Actual results:
New resource and bucket are reported in console as healthy.

Expected results:
Resource should be in error state and it should not be possible to create a bucket with it.

Additional info:
Comment 6 Filip Balák 2021-02-23 14:28:06 UTC 
The fix seems to work for namespace resources created via both NooBaa Console and OpenShift CRDs. --> VERIFIED

Tested with:
OCS ocs-operator.v4.7.0-270.ci
OCP 4.8.0-0.nightly-2021-02-23-013453
Comment 9 errata-xmlrpc 2021-05-19 09:16:24 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 Container Storage 4.7.0 security, bug fix, and enhancement 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:2041