Bug 2314900
| Summary: | NooBaa CLI: Attempting to delete a bucketclass or OBC that don't exist doesn't result in an error | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Sagi Hirshfeld <shirshfe> |
| Component: | Multi-Cloud Object Gateway | Assignee: | Nimrod Becker <nbecker> |
| Status: | NEW --- | QA Contact: | krishnaram Karthick <kramdoss> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.17 | CC: | 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: | |||
Description of problem (please be detailed as possible and provide log snippests): ------------------------------------------------------------------------ Using the noobaa CLI to delete a bucketclass that doesn't exist does not result in an error as expected: ``` $ noobaa bucketclass delete non-existant-bc | grep -i err || echo "No errors :(" No errors :( ``` Version of all relevant components (if applicable): ------------------------------------------------------------------------ ODF: 4.17.0-108 noobaa core: 5.17.0-b1c72eb noobaa operator: 5.17.0-890badeb954acea07365f204e20f9443970dc560 noobaa cli: 5.17.0 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? ------------------------------------------------------------------------ Mildly - the issue here is mainly inconsistency since 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. 2. 3. Actual results: Expected results: Additional info: