Bug #50554
radosgw-admin user create error message is confusing if user with supplied email address already exists
0%
Description
This is a copy of https://tracker.ceph.com/issues/49137
The patch/fix there was incorrectly applied to a different function (PR: https://github.com/ceph/ceph/pull/39293).
(Below is the original 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 Ponnuvel P about 2 years ago
- Copied from Bug #49137: radosgw-admin user create error message is confusing if user with supplied email address already exists added
#2 Updated by Ponnuvel P about 2 years ago
- Pull request ID set to 41065
#3 Updated by Casey Bodley about 2 years ago
- Status changed from New to Fix Under Review
#4 Updated by J. Eric Ivancich almost 2 years ago
- Status changed from Fix Under Review to Pending Backport
#5 Updated by Backport Bot almost 2 years ago
- Copied to Backport #51139: octopus: radosgw-admin user create error message is confusing if user with supplied email address already exists added
#6 Updated by Backport Bot almost 2 years ago
- Copied to Backport #51140: pacific: radosgw-admin user create error message is confusing if user with supplied email address already exists added
#7 Updated by Backport Bot almost 2 years ago
- Copied to Backport #51141: nautilus: radosgw-admin user create error message is confusing if user with supplied email address already exists added
#8 Updated by Ponnuvel P 11 months ago
- Status changed from Pending Backport to Resolved