Bug 2211871

Summary: [GSS][Noobaa] when creating an OBC with noobaa storageclass the status of the object is LOST/unknown
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Karun Josy <kjosy>
Component: Multi-Cloud Object GatewayAssignee: Nimrod Becker <nbecker>
Status: CLOSED INSUFFICIENT_DATA QA Contact: krishnaram Karthick <kramdoss>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.12CC: hnallurv, lmauda, nbecker, ocs-bugs, odf-bz-bot
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-28 10:55:40 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 Karun Josy 2023-06-02 12:14:27 UTC 
# Description of problem (please be detailed as possible and provide log
snippests):

Customer is experiencing problems with the creation of object bucket claims (OBC) for object storage. When creating an Object Bucket Claim with noobaa storageclass the status of the object is LOST/unknown. 

Customer was able to create OBC before without any issues.
No changes have been made to the cluster since then.

# Version of all relevant components (if applicable):
ODF 4.12

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

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


Additional info:
More details in the following comment