tempest.api.network.test_extensions.ExtensionsTestJSON.test_list_show_extensions fails extensions order differ

[Fabian Zimmermann]

Looks like tempest.api.network.test_extensions.ExtensionsTestJSON.test_list_show_extensions is failing if the order of returned extension-list differ.

Im running an HA-pair of control-ndoes. It looks like the order depends on the host the request is hitting.

So, if the 1st request and the "compare" request do not hit the same backend, my test is failing with:

tempest.api.network.test_extensions.ExtensionsTestJSON.test_list_show_extensions
--------------------------------------------------------------------------------
Traceback (most recent call last):
  File "tempest/api/network/test_extensions.py", line 62, in test_list_show_extensions
    self.assertEqual(ext_details['name'], ext_name)
  File "/home/rally/.rally/verification/verifier-3f3badb7-1158-4cf0-b46d-ea7740a6643f/.venv/local/lib/python2.7/site-packages/testtools/testcase.py", line 411, in assertEqual
    self.assertThat(observed, matcher, message)
  File "/home/rally/.rally/verification/verifier-3f3badb7-1158-4cf0-b46d-ea7740a6643f/.venv/local/lib/python2.7/site-packages/testtools/testcase.py", line 498, in assertThat
    raise mismatch_error
testtools.matchers._impl.MismatchError: !=:
reference = u'Tag support for resources with standard attribute: floatingip, security_group, policy, trunk'
actual = u'Tag support for resources with standard attribute: floatingip, trunk, security_group, policy'

[Fabian Zimmermann (dev-faz)]

took a look into the code. The problem is *not* the order of ext, its the "name"-field of the tag-ext extension.

openstack extension show tag-ext -c name -f value
Tag support for resources: router, subnetpool, port, subnet
openstack extension show tag-ext -c name -f value
Tag support for resources: router, subnetpool, port, subnet
openstack extension show tag-ext -c name -f value
Tag support for resources: router, subnetpool, port, subnet
openstack extension show tag-ext -c name -f value
Tag support for resources: router, subnetpool, port, subnet
openstack extension show tag-ext -c name -f value
Tag support for resources: router, subnetpool, port, subnet
openstack extension show tag-ext -c name -f value
Tag support for resources: subnet, subnetpool, port, router

as you can see, the content of the name-field changes, which will trigger the test-failure.

Dont know if this is a bug in neutron or tempest?!

[Martin Kopec (mkopec)]

Is this still reproducible?
I checked the code and I don't see anything which could cause such an issue. The test list extensions available and then iterates over them while it takes the alias of the extension, requests details through that alias and checks if the name in the details is the same as was listed at the beginning of the test.
Let us know, if you still experience the issue. I'm gonna mark this as incomplete as I'm gonna need more info to debug it further.

[Launchpad Janitor (janitor)]

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