Bug 1900760
| Summary: | RPC call for Namespace resource creation allows invalid target bucket names | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Container Storage | Reporter: | Filip Balák <fbalak> | ||||
| Component: | Multi-Cloud Object Gateway | Assignee: | Jacky Albo <jalbo> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Filip Balák <fbalak> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 4.6 | CC: | ebenahar, etamir, muagarwa, nbecker, ocs-bugs | ||||
| Target Milestone: | --- | ||||||
| Target Release: | OCS 4.7.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | v4.7.0-229.ci | Doc Type: | If docs needed, set a value | ||||
| 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: | |||||||
| Attachments: |
|
||||||
Following a triage meeting, moving to 4.7 When invalid bucket name is provided, message "Target bucket doesn't exist" is in response and namespace resource is not created. --> VERIFIED Tested with: ocs-operator.v4.7.0-236.ci Nimrod, do we need doc text for this? 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 1732620 [details] Namespace Resources tab Description of problem (please be detailed as possible and provide log snippests): RPC call for Namespace resource creation allows invalid target bucket names like epmty string or special characters. This can lead to unexpected behaviour. 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? No, only by using developer tools in browser. Steps to Reproduce: 1. Create connection Connection1 in Multi Cloud Object Gateway. 2. Send RPC with parameters: "pool_api", "create_namespace_resource", {"name": "invalid_resource", "connection": "Connection1", "target_bucket": ""} Actual results: RPC successfully passes and the resource is created. Resource called "invalid_resource" is created and its target bucket is set to [object Object]. It is reported as healthy in console and there can be created Namespace bucket with it. Expected results: RPC call should fail and in response should be appropriate error message. Additional info: