yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #79421
[Bug 1836618] Re: Due to case sensitivity of a user name compare in a keystone test, the test might fail
Thanks for adding the more info. That seems strange for me that username
is not kept same as it was input. case sensitive in keystone is based on
backend but it should be consistent.
I am adding keystone as an affected project in this bug to get provide
input on why returned user name is not consistent in term of case
sensitive.
** Also affects: keystone
Importance: Undecided
Status: New
--
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/1836618
Title:
Due to case sensitivity of a user name compare in a keystone test, the
test might fail
Status in OpenStack Identity (keystone):
New
Status in tempest:
In Progress
Bug description:
Due to case sensitivity of a user name compare in a keystone test, the test might return an error similar to the one below:
Captured Traceback:
Traceback (most recent call last):
File "tempest/api/identity/v3/test_tokens.py", line 113, in test_token_auth_creation_existence_deletion
self.assertEqual(token_details['user']['name'], user.username)
File "/home/manasareddybethi/aqua-venv/local/lib/python2.7/site-packages/testtools/testcase.py", line 411, in assertEqual
self.assertThat(observed, matcher, message)
File "/home/manasareddybethi/aqua-venv/local/lib/python2.7/site-packages/testtools/testcase.py", line 498, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: u'KellyTest' != u'kellytest'
This is because it is comparing the name from keystone and the name from tempest.conf or accounts.yaml, when using preprovisioned creds. Here is he example that I have on our openstack instance.
mismatch error from the stack trace, u'KellyTest' != u'kellytest'
the username for the project and username on accounts.yaml or tempest.conf are not identical.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1836618/+subscriptions