Bug 2322178
| Summary: | [UI] Error message Popup fail to alert on rule: Cannot be used before | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Daniel Osypenko <dosypenk> | ||||
| Component: | management-console | Assignee: | Nishanth Thomas <nthomas> | ||||
| Status: | NEW --- | QA Contact: | Prasad Desala <tdesala> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.17 | CC: | asriram, odf-bz-bot | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 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 2054081 [details] all-green-validation Description of problem (please be detailed as possible and provide log snippests): When creating OBC being in different namespace popup doesn't notify user on OBC already being created by one of the reasons: 1. It is allowed to have two OBCs with the same name on different namespaces (not sure if it is considered a good practice and we'd want to allow user to have it?) 2. It is not allowed to have two OBCs with the same name on different namespaces but we don't track OBCs across all namespaces Version of all relevant components (if applicable): 4.15 and above. Last reproduction on ODF 4.17.0-126 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? Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Create OBC with a name oc-bucket-0a1b5eccb8dc467cb71a3667d45e38 in ns "openshift-storage" kind: ObjectBucketClaim metadata: name: oc-bucket-0a1b5eccb8dc467cb71a3667d45e38 namespace: openshift-storage spec: additionalConfig: bucketclass: oc-bucketclass-106f2a5e4f7841a18d6a04721 bucketName: oc-bucket-0a1b5eccb8dc467cb71a3667d45e38 storageClassName: openshift-storage.noobaa.io 2. Create OBC with a same name in a different namespace, for example "default" 3. Actual results: "Cannot be used before" - does not appear Expected results: "Cannot be used before" - notification becomes red signaling violation or we need to fix msg to "Cannot be used before within same namespace" Additional info: