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