Tempest heat test calls keystone v3 user api with domain_id

Bug #1283539 reported by Henry Nash
6
This bug affects 1 person
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.api.orchestration.stacks.test_templates.TemplateYAMLTestJSON)
2014-02-22 19:35:20.782 | setUpClass (tempest.api.orchestration.stacks.test_templates.TemplateYAMLTestJSON)
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/api/orchestration/stacks/test_templates.py", line 39, in setUpClass
2014-02-22 19:35:20.783 | 'CREATE_COMPLETE')
2014-02-22 19:35:20.783 | File "tempest/services/orchestration/json/orchestration_client.py", line 185, in wait_for_stack_status
2014-02-22 19:35:20.783 | stack_status_reason=body['stack_status_reason'])
2014-02-22 19:35:20.784 | StackBuildErrorException: Stack heat-1428463818/8e6771cb-9b28-4118-b237-e37d556d15a1 is in CREATE_FAILED status due to 'Resource create failed: BadRequest: domain_id is required as part of v3 entity (HTTP 400)'
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.api.orchestration.stacks.test_templates.TemplateAWSTestJSON)
2014-02-22 19:35:20.785 | setUpClass (tempest.api.orchestration.stacks.test_templates.TemplateAWSTestJSON)
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/api/orchestration/stacks/test_templates.py", line 39, in setUpClass
2014-02-22 19:35:20.786 | 'CREATE_COMPLETE')
2014-02-22 19:35:20.787 | File "tempest/services/orchestration/json/orchestration_client.py", line 185, in wait_for_stack_status
2014-02-22 19:35:20.787 | stack_status_reason=body['stack_status_reason'])
2014-02-22 19:35:20.787 | StackBuildErrorException: Stack heat-2066870201/baa1f6fd-0f2f-4f55-bbe7-cfe4f0c4dc28 is in CREATE_FAILED status due to 'Resource create failed: BadRequest: domain_id is required as part of v3 entity (HTTP 400)'
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.

Revision history for this message
David Kranz (david-kranz) wrote :

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?

Changed in tempest:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for tempest because there has been no activity for 60 days.]

Changed in tempest:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.