[Bug 1940456] Re: [SRU] radosgw-admin's diagnostics are confusing if user data exists

[Dan Hill]

** Changed in: cloud-archive
       Status: New => Fix Released

** Changed in: ceph (Ubuntu)
       Status: New => Fix Released

-- 
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/1940456

Title:
  [SRU] radosgw-admin's diagnostics are confusing if user data exists

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive ussuri series:
  Fix Released
Status in Ubuntu Cloud Archive victoria series:
  Invalid
Status in Ubuntu Cloud Archive wallaby series:
  Fix Released
Status in Ubuntu Cloud Archive xena series:
  Fix Released
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:
  Fix Released
Status in ceph source package in Hirsute:
  Fix Released

Bug description:
  This is same as LP#1914584 but its original patch was wrong which was
  found out in SRU tests and that particular release went ahead without
  the patch. Since that LP is kind of in hard-to-follow/confusing
  states, opened this new bug to carry out the SRU work.

  ----------

  [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 Ponnuvel Palaniyappan (attached here)
  - Upstream tracker: https://tracker.ceph.com/issues/50554
  - Upstream PR: https://github.com/ceph/ceph/pull/41065
  - Backported to Pacific, and Octopus upstream releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1940456/+subscriptions