Bug #49137
radosgw-admin user create error message is confusing if user with supplied email address already exists
0%
Description
Hi,
If you try and create an S3 user account with an email address that's already in use, you get a very confusing error message.
Suppose that bar@domain is already in use for an S3 account uid=baz
radosgw-admin user create --uid=foo --display-name=Foo --email=bar@domain
will return something like:
could not create user: unable to parse parameters, user id mismatch, operation id: baz does not match: foo
...which is pretty confusing.
I think I have a patch to make the error message more helpful, but thought I should put in a tracker issue in the mean time. I found this in Luminous, but it's still present in master.
Related issues
History
#1 Updated by Matthew Vernon over 2 years ago
https://github.com/ceph/ceph/pull/39293 opened which fixes this.
#2 Updated by Casey Bodley over 2 years ago
- Status changed from New to Fix Under Review
- Backport set to pacific octopus nautilus
- Pull request ID set to 39293
#3 Updated by Ponnuvel P over 2 years ago
I'd like to backport to the stable releases. Can someone change the Status from "Fix Under Review" to "Pending Backport" please?
#4 Updated by Dan Hill over 2 years ago
- Status changed from Fix Under Review to Pending Backport
Merged into master on Feb 18, 2021.
#5 Updated by Backport Bot over 2 years ago
- Copied to Backport #49440: nautilus: radosgw-admin user create error message is confusing if user with supplied email address already exists added
#6 Updated by Backport Bot over 2 years ago
- Copied to Backport #49441: octopus: radosgw-admin user create error message is confusing if user with supplied email address already exists added
#7 Updated by Backport Bot over 2 years ago
- Copied to Backport #49442: pacific: radosgw-admin user create error message is confusing if user with supplied email address already exists added
#8 Updated by Yuri Weinstein over 2 years ago
#9 Updated by Nathan Cutler about 2 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" or "Rejected".
#10 Updated by Ponnuvel P about 2 years ago
- Copied to Bug #50554: radosgw-admin user create error message is confusing if user with supplied email address already exists added