[Bug 1914584] Re: [SRU] radosgw-admin user create error message confusing if user with email already exists

[James Page]

Comments #19 and #20 probably relate to some tasks being marked as Fix
Released due to the way that the proposed -> updates migration works -
the changelog is generated based on what's already in updates for the
migration.  Thus the bug fixed in the first uploaded but then reverted
in the second gets marked as Fix Released.

The fix that is being worked on still resolves *this* bug so I think re-
use is OK - when I discussed with sil21000 whilst working on the revert
we agreed that the tasks would need to be reset once the update was
released (and that this was less than ideal).

Anyway I hope that provides some context for this discussion.

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1914584

Title:
  [SRU] radosgw-admin user create error message confusing if user with
  email already exists

Status in Ceph:
  Unknown
Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive queens series:
  Won't Fix
Status in Ubuntu Cloud Archive rocky series:
  Won't Fix
Status in Ubuntu Cloud Archive stein series:
  Won't Fix
Status in Ubuntu Cloud Archive train series:
  Won't Fix
Status in Ubuntu Cloud Archive ussuri series:
  New
Status in Ubuntu Cloud Archive victoria series:
  New
Status in ceph package in Ubuntu:
  Fix Released
Status in ceph source package in Bionic:
  Won't Fix
Status in ceph source package in Focal:
  Won't Fix
Status in ceph source package in Groovy:
  Won't Fix
Status in ceph source package in Hirsute:
  Won't Fix

Bug description:
  [Impact]

  When creating a new S3 user, the error message is confusing if the
  email address used is already associated with another S3 account.

  To reproduce:

  radosgw-admin user create --uid=foo --display-name="Foo test" --email=bar at domain.invalid
  #[ success ]
  radosgw-admin user create --uid=test --display-name="AN test" --email=bar at domain.invalid
  could not create user: unable to parse parameters, user id mismatch, operation id: foo does not match: test

  As a result, it's completely unclear what went wrong with the user
  creation.

  [Test case]

  Create an S3 account via radosgw-admin. Then create another user but use
  the same email address - it should provide a clear description of what
  the problem is.

  [Where problems could occur]

  The new message may yet be unclear or could complain that an email
  exists even though it doesn't exist (false positive). It's an improved
  diagnostic by checking if the email id exists. Perhaps, user creation
  might become problematic if the fix doesn't work.

  [Other Info]
  - The patch was provided by Matthew Vernon (attached here)
  - Upstream tracker: https://tracker.ceph.com/issues/49137
  - Upstream PR: https://github.com/ceph/ceph/pull/39293
  - Backported to Pacific, Octopus, and Nautilus upstream releases. Luminous is EOL'ed upstream, so we'd like to backport to Luminous (Bionic/queens).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceph/+bug/1914584/+subscriptions