yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #66366
[Bug 1688188] Re: Handle auto created domain when creating duplicate idp in federation
Reviewed: https://review.openstack.org/462408
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=6e60948c20e9a8fe5469bb7735641026a1f36cd5
Submitter: Jenkins
Branch: master
commit 6e60948c20e9a8fe5469bb7735641026a1f36cd5
Author: yangweiwei <yangweiwei@xxxxxxxxxxxxxxxxxxxx>
Date: Thu Jun 29 18:49:33 2017 +0800
Handle auto-generated domains when creating IdPs
When creating an IdP, if a domain was generated for it and a conflict
was raised while effectively creating the IdP in the database, the
auto-generated domain is now cleaned up.
Change-Id: I9b7c3c1fae32b9412f75323a75d9ebe4ad756729
Closes-Bug: #1688188
** Changed in: keystone
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1688188
Title:
Handle auto created domain when creating duplicate idp in federation
Status in OpenStack Identity (keystone):
Fix Released
Bug description:
If we create an idp with ID 'keystone-ipd', then we create idp with the same ID.
We get the result like 'conflict happens', it is ok.
But when I see the domain list. the auto generated domain still here.
I think, the second idp was created failed, then the resource auto generated it used should be cleared.
If we create an idp specifing the domain, the idp was created failed and the specifing domain was not auto generated, so the resource should not be cleared.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1688188/+subscriptions
References