Tempest heat test calls keystone v3 user api with domain_id
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Expired
|
Undecided
|
Unassigned |
Bug Description
The keystone v3 api for creating users/groups require, as per the identity-api specification, that either a domain_id is explicitly specified in the entity, or a domain scoped token is used (and the scope of the token is taken as the domain_id). The tempest heat test appears to do neither of these things. At the moment, the keystone code (incorrectly) catches this error and assumes the default domain (i.e. it treats the v3 call like a v2 call). This isn't a safe assumption, and we need to remove this code. If we do so, we get the following errors:
=======
2014-02-22 19:35:20.781 | FAIL: setUpClass (tempest.
2014-02-22 19:35:20.782 | setUpClass (tempest.
2014-02-22 19:35:20.782 | -------
2014-02-22 19:35:20.782 | _StringException: Traceback (most recent call last):
2014-02-22 19:35:20.782 | File "tempest/
2014-02-22 19:35:20.783 | 'CREATE_COMPLETE')
2014-02-22 19:35:20.783 | File "tempest/
2014-02-22 19:35:20.783 | stack_status_
2014-02-22 19:35:20.784 | StackBuildError
2014-02-22 19:35:20.784 |
2014-02-22 19:35:20.784 |
2014-02-22 19:35:20.785 | =======
2014-02-22 19:35:20.785 | FAIL: setUpClass (tempest.
2014-02-22 19:35:20.785 | setUpClass (tempest.
2014-02-22 19:35:20.785 | -------
2014-02-22 19:35:20.786 | _StringException: Traceback (most recent call last):
2014-02-22 19:35:20.786 | File "tempest/
2014-02-22 19:35:20.786 | 'CREATE_COMPLETE')
2014-02-22 19:35:20.787 | File "tempest/
2014-02-22 19:35:20.787 | stack_status_
2014-02-22 19:35:20.787 | StackBuildError
2014-02-22 19:35:20.788 |
2014-02-22 19:35:20.788 |
We'll keep the current code in place until this can get fixed.
I looked at the code and don't see where the v3 calls are not passing domain_id. Can you provide the tempest log for this run and the identity part of tempest.conf?