Actions
Bug #41589
closedif user doesnt exist then bucket list should give error/info message (saying user doesnt exist) rather than showing empty list
% Done:
0%
Source:
Tags:
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
https://bugzilla.redhat.com/show_bug.cgi?id=1747516
- It should say --uid empty.
[root@3cfea3e7c7e2 build]# bin/radosgw-admin bucket list --uid= [ "my-new-bucket5", "my-new-bucket1", "my-new-bucket3", "my-new-bucket4", "my-new-bucket2" ]
- It should say user does not exist.
[root@3cfea3e7c7e2 build]# bin/radosgw-admin user list [ "56789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234", "testx$9876543210abcdef0123456789abcdef0123456789abcdef0123456789abcdef", "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef", "test", "testid" ] [root@3cfea3e7c7e2 build]# bin/radosgw-admin bucket list --uid=abcd []
Updated by Vikhyat Umrao over 4 years ago
- Status changed from New to In Progress
- Assignee set to Vikhyat Umrao
Updated by Vikhyat Umrao over 4 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 30194
Updated by Casey Bodley over 4 years ago
- Status changed from Fix Under Review to 7
Updated by Vikhyat Umrao over 4 years ago
- Status changed from Resolved to Pending Backport
- Backport set to nautilus
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #41976: nautilus: if user doesnt exist then bucket list should give error/info message (saying user doesnt exist) rather than showing empty list added
Updated by Nathan Cutler over 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved".
Actions