Unexpected failure when accounts.yaml doesn't have user ID
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I have a simple accounts.yaml where I only specify the usernames and tenant ID:
- username: 'user1'
tenant_id: 'user1_tenant_id'
password: 'user1_password'
- username: 'user2'
tenant_id: 'user2_tenant_id'
password: 'user2_password'
A lot of tests pass with just this info because tempest is able to get a token just fine using the username, password, and project ID.
But the tempest.
Traceback (most recent call last):
File "/opt/openstack
File "/opt/openstack
File "/opt/openstack
raise mismatch_error
testtools.
Since the creds doesn't have the user ID, it's trying to match the token's userID with the nonexistant userID in accounts.yaml and failing.
This test should have passed. Tempest doesn't know what the user ID is supposed to be since it's not specified in accounts.yaml so it should just verify that a user ID is present in the token.
Alternatively, tempest could look up the user and check that the ID in the token matches the user's ID.
Changed in tempest: | |
assignee: | nobody → Brant Knudson (blk-u) |
Changed in tempest: | |
assignee: | Brant Knudson (blk-u) → nobody |
Fix proposed to branch: master /review. openstack. org/388897
Review: https:/