Bug 2026556

Summary: Unable to create new MCG OBC
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Dirk Haubenreisser <dhaubenr>
Component: Multi-Cloud Object GatewayAssignee: Evgeniy Belyi <ebelyi>
Status: CLOSED NOTABUG QA Contact: Raz Tamir <ratamir>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.9CC: belimele, etamir, mmuench, nbecker, ocs-bugs, odf-bz-bot
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-29 12:29:48 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 Dirk Haubenreisser 2021-11-25 05:58:28 UTC
Description of problem (please be detailed as possible and provide log
snippests):

The ocs-ci testcase 'tests/manage/mcg/test_namespace_rpc.py::TestNamespace::test_delete_resource_used_in_ns_bucket_rpc' fails due to the OBC not being created as expected: 'Error from server (NotFound): objectbucketclaims.objectbucket.io "mcg-namespace-bucket-ad5ed16abeba4cc3acb" not found'.


Version of all relevant components (if applicable):

OCP: 4.9.7

---------- oc -n openshift-storage get csv ----------
NAME                  DISPLAY                       VERSION   REPLACES   PHASE
mcg-operator.v4.9.0   NooBaa Operator               4.9.0                Succeeded
ocs-operator.v4.9.0   OpenShift Container Storage   4.9.0                Succeeded
odf-operator.v4.9.0   OpenShift Data Foundation     4.9.0                Succeeded


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

Yes, if no OBCs are created properly the feature is not usable at all?


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)?

4


Can this issue reproducible?

Yes, reran the ocs-ci testcase 'tests/manage/mcg/test_namespace_rpc.py::TestNamespace::test_delete_resource_used_in_ns_bucket_rpc' many times and always got the same result.


Can this issue reproduce from the UI?

n/a


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Run the ocs-ci testcase 'tests/manage/mcg/test_namespace_rpc.py::TestNamespace::test_delete_resource_used_in_ns_bucket_rpc'


Actual results:
The new OBC 'mcg-namespace-bucket-ad5ed16abeba4cc3acb' is not being created properly.


Expected results:
A new OBC is expected to be created properly bc MCG.


Additional info:

n/a

Comment 2 Nimrod Becker 2021-11-25 07:39:29 UTC
logs ? must-gather?

Comment 3 Dirk Haubenreisser 2021-11-25 09:56:37 UTC
I've assembled all logs but the resulting tar.gz file is too large to be attached to this ticket. Any idea where to put it instead?

Comment 4 Dirk Haubenreisser 2021-11-25 10:36:23 UTC
Nevermind, found a way... you'll find the tar.gz file with all test case logs and must_gather logs here: https://drive.google.com/drive/folders/1H21p5uEIEaqVJQj-fooD5aFpWxKo-FHW?usp=sharing

Comment 8 Dirk Haubenreisser 2021-11-29 06:08:46 UTC
I had a look at the corresponding code dealing with the MCG RPC API in ocs-ci and I couldn't find anything that sticks out - from what I can tell, the code is handling the RPC API correctly: https://github.com/red-hat-storage/ocs-ci/blob/a8c4a806c295677be565cba42e33a747b5908bca/ocs_ci/ocs/resources/objectbucket.py#L504

Reopening this ticket as further assistance from DEV is needed for debugging the issue.

Comment 9 Ben Eli 2021-11-29 12:29:48 UTC
After talking with Dirk, we realized that his Bugzilla account does not have the required permissions to view private comments.
We have debugged the reason that the test was not skipped, even though his environment was correctly set to 'ocs_version': '4.9'.
The reason was that 'skip_ocs_deployment' was set to 'true', meaning that none of the skipif markers were collected or respected by the test suite.

An OCS-CI issue was filed - https://github.com/red-hat-storage/ocs-ci/issues/5148

Closing the bug by Dirk's request.