Bug 2043572 - [UI] Deleting namespace store in UI
 : secrets remains
Summary: [UI] Deleting namespace store in UI
 : secrets remains
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.9
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
: ODF 4.12.0
Assignee: Debjyoti Pandit
QA Contact: Vishakha Kathole
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-21 14:29 UTC by Marc Schindler
Modified: 2023-08-09 16:46 UTC (History)
11 users (show)

Fixed In Version: 4.12.0-74
Doc Type: Bug Fix
Doc Text:
Cause: While creating NSS/BSS UI creates (if opted) a Secret as well using the name of the NSS/BSS under creation. Consequence: If NSS/BSS is deleted after creation and then created again with same name then when UI will try to create a Secret using this NSS/BSS name it will face an error as Secret will already be existing with that name (did not get deleted along with NSS/BSS deletion). Fix: If Secret already exists, along with NSS/BSS name random character will get added to the string which then will be used as a Secret name while its creation. Result: No more error on UI. Note: NSS >> NameSpaceStore BSS >> BackingStore
Clone Of:
Environment:
Last Closed: 2023-02-08 14:06:28 UTC
Embargoed:

Attachments (Terms of Use)
UI error and workaround via noobaa cli (755.81 KB, image/png)
2022-01-21 14:29 UTC, Marc Schindler 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage odf-console pull 410 0 None open Bug 2043572: adding random characters if secret exists with same name during nss creation 2022-09-20 13:23:28 UTC

Description Marc Schindler 2022-01-21 14:29:11 UTC 
Created attachment 1852517 [details]
UI error and workaround via noobaa cli

Deleting namespace store in the UI


Issue: secrets not deleted in the background
Improvement: Ask if it can be delete or not would improve UX


Is there any workaround available to the best of your knowledge?
Yes, delete secret manually or delete namespace via noobaa cli

Picture attached, which shows on the left corner noobaa cli and on the right corner the UI error message after creating the namespace store with the same name as before again.

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?
Yes

Can this issue reproduce from the UI?
Yes
Comment 23 Sanjal Katiyar 2023-01-09 15:51:30 UTC 
added doc text...
Note You need to log in before you can comment on or make changes to this bug.