order of user list appears inconsistent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Priti Desai |
Bug Description
This appeared as a transient failure in a doc change. I suspect the test shouldn't bother asserting the order of the results, only that the expected values appear in the list.
=======
FAIL: keystone.
tags: worker-1
-------
Empty attachments:
pythonlogging
stderr
stdout
pythonlogging:'': {{{
Adding cache-proxy 'keystone.
KVS region configuration for token-driver: {'keystone.
Using default dogpile sha1_mangle_key as KVS region token-driver key_mangler
It is recommended to only use the base key-value-store implementation for the token driver for testing purposes. Please use keystone.
KVS region configuration for os-revoke-driver: {'keystone.
Using default dogpile sha1_mangle_key as KVS region os-revoke-driver key_mangler
Callback: `keystone.
Callback: `keystone.
Callback: `keystone.
Callback: `keystone.
Callback: `keystone.
Callback: `keystone.
Callback: `keystone.
Callback: `keystone.
Callback: `keystone.
found extension EntryPoint.
found extension EntryPoint.
found extension EntryPoint.
found extension EntryPoint.
found extension EntryPoint.
found extension EntryPoint.
found extension EntryPoint.
found extension EntryPoint.
found extension EntryPoint.
found extension EntryPoint.
found extension EntryPoint.
User 70bb7abd662a42c
}}}
Traceback (most recent call last):
File "keystone/
self.
File "/home/
self.
File "/home/
raise mismatch_error
MismatchError: !=:
reference = {'users': [{'email': '<email address hidden>',
'id': 'd00764bbd27f47
'name': 'FOO',
'id': 'ee5f3d2c210e48
'name': 'SNA',
actual = {'users': [{'email': '<email address hidden>',
'id': 'ee5f3d2c210e48
'name': 'SNA',
'id': 'd00764bbd27f47
'name': 'FOO',
description: | updated |
tags: | added: transient |
Changed in keystone: | |
assignee: | nobody → Priti Desai (priti-desai) |
Changed in keystone: | |
status: | Triaged → In Progress |
Changed in keystone: | |
milestone: | none → juno-2 |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | juno-2 → 2014.2 |
Reviewed: https:/ /review. openstack. org/101712 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=7b339d1ff85 ba7819e60459bdd ed48019ea9bd56
Committed: https:/
Submitter: Jenkins
Branch: master
commit 7b339d1ff85ba78 19e60459bdded48 019ea9bd56
Author: Priti Desai <email address hidden>
Date: Sat Jun 21 17:34:45 2014 +0000
Ignoring order of user list in TenantTestCase
keystone. tests.test_ v2_controller. TenantTestCase. get_project_ users_no_ user should not bother asserting l(orig_ project_ users, new_project_users) l(sorted( orig_project_ users), sorted( new_project_ users))
test_
the order of the results, only that the expected values appear in the list.
Replacing self.assertEqua
with self.assertEqua
Better option would be assertItemsEqual but its only available in 2.7 and later.
Closes-bug: #1332831 a8908241498e1cc 794e04d992c
Change-Id: I09842e0375dc0f