yahoo-eng-team team mailing list archive

[Alexander Makarov <amakarov@xxxxxxxxxxxx>]

Public bug reported:

Scenario:

2 requests are executed in parallel:
1) authentication against "the tenant" by tenant name
2) delete "the tenant" + create "the tenant"

According to API contract authentication should pass, but internally all magic is done using tenant_id acquired at the very beginning of the request (1).
So while formally tenant named "the tenant" exists, authentication fails as it's no mode accessible by it's old id.

** Affects: keystone
     Importance: Undecided
         Status: New

** Summary changed:

- AuthN fails if the projects is recreated in the process
+ AuthN fails if the tenant is recreated in the process

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1494398

Title:
  AuthN fails if the tenant is recreated in the process

Status in Keystone:
  New

Bug description:
  Scenario:

  2 requests are executed in parallel:
  1) authentication against "the tenant" by tenant name
  2) delete "the tenant" + create "the tenant"

  According to API contract authentication should pass, but internally all magic is done using tenant_id acquired at the very beginning of the request (1).
  So while formally tenant named "the tenant" exists, authentication fails as it's no mode accessible by it's old id.

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