Bug 2151903
| Summary: | [MCG] Azure bs/ns creation fails with target bucket does not exists | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Parikshith <pbyregow> | |
| Component: | Multi-Cloud Object Gateway | Assignee: | Nobody <nobody> | |
| Status: | CLOSED ERRATA | QA Contact: | Sagi Hirshfeld <shirshfe> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.12 | CC: | muagarwa, nbecker, nobody, ocs-bugs, odf-bz-bot, usrivast | |
| Target Milestone: | --- | |||
| Target Release: | ODF 4.13.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | 4.13.0-39 | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2165493 (view as bug list) | Environment: | ||
| Last Closed: | 2023-06-21 15:22:18 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 2165493 | |||
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 (Red Hat OpenShift Data Foundation 4.13.0 enhancement and bug fix 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/RHBA-2023:3742 |
Description of problem (please be detailed as possible and provide log snippests): Even though target azure container exists in the backend, Azure bs/ns creation fails with "target bucket does not exists" if there are already large number of azure blob containers present. $az storage container exists --account-name *** --account-key *** -n temp-azure { "exists": true } $noobaa backingstore create azure-blob temp-az2 --account-key *** --account-name *** --target-blob-container temp-azure - lastHeartbeatTime: "2022-12-06T12:01:38Z" lastTransitionTime: "2022-12-06T12:01:38Z" message: Target bucket doesn't exist reason: TemporaryError status: "False" type: Upgradeable Version of all relevant components (if applicable): Noticed on ODF 4.8-4.12 runs 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? yes, reduce the count of azure containers Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 2 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: no Steps to Reproduce: 1. Have more than 100 target blob containers present in azure 2. Create a new bs/ns with a target container Actual results: BS/NS creation fails with target bucket already exists Expected results: BS/NS creation should pass irrespective of how many target azure containers present in the back end. Additional info: