[RBAC] Backup storages page is empty if user only has access to a single storage
Description
User impact:
Restricting access to a single backup storage hides all storages making this configuration useless.
Steps to reproduce:
Create 2 backup storages storage-a and storage-b in namespaceA.
Add the following RBAC policy:
Actual result:
The backup storages page is empty
Expected result:
The backup storages page should only contain the monitoring-a instance.
Workaround (if one exists):
Environment:
Environment
None
Attachments
1
100% Done
Activity
Show:
Edith Erika Puclla Pareja December 30, 2024 at 11:25 AM
FYI, I tested this and it is working fine, but created just one improvement:
Diogo Recharte December 27, 2024 at 3:15 PM
please close this bug and create an improvement ticket for updating the backup storages page automatically.
Edith Erika Puclla Pareja December 27, 2024 at 3:03 PM
I tested this ticket with the following:
I created two storages, test-storage01 and test-storage02 in S3
Created a new user testuser using everstctl and I logged in with this user in Everest
I updated the RBAC policy to this:
I noticed that when any update in the policy is made, for example, for user storageA or storageB, this is immediately updated in the screen of `Backup Storages`, but when we first time configure a new policy to access a single storage, the changes are not reflected immediately in the screen, en el video 00:46
I think the expected result should be that it updates automatically without having to click on another component to refresh the screen.
User impact:
Restricting access to a single backup storage hides all storages making this configuration useless.
Steps to reproduce:
Create 2 backup storages
storage-aandstorage-binnamespaceA.Add the following RBAC policy:
Actual result:
The backup storages page is empty
Expected result:
The backup storages page should only contain the
monitoring-ainstance.Workaround (if one exists):
Environment: