Bug 1937768
| Summary: | OBC with Cache BucketPolicy stuck on pending | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Container Storage | Reporter: | aberner | ||||||
| Component: | Multi-Cloud Object Gateway | Assignee: | Jacky Albo <jalbo> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Ben Eli <belimele> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 4.7 | CC: | belimele, ebenahar, etamir, jthottan, muagarwa, nbecker, nobody+410372, ocs-bugs | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | OCS 4.7.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2021-05-19 09:20:45 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: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1762670 [details]
noobaa diag
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 |
Created attachment 1762669 [details] test run logs Description of problem (please be detailed as possible and provide log snippests): While trying to create an OBC as part of a test the OBC never reached Bound state, i've looked into the operator's logs and there werent any suggesting the bucket reached bound state but later on in the teardown there was a log with a changed status from bound to released. I've attached noobaa diagnose and the test run to the bug, and the cluster is still running atm. Version of all relevant components (if applicable): OCS: 4.7.0-286.ci OCP: 4.7.0-0.nightly-2021-03-10-202622 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? 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)? 1 Can this issue reproducible? not yet tested Can this issue reproduce from the UI? not yet tested If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. run the test_base_operation_node_restart from the ocs-ci test suit 2. 3. Actual results: OBC stuck on Pending Expected results: OBC gets to status bound Additional info: