HTTP 409 Conflict in functional tests

[Brian Curtin]

I don't even know what this is yet, but it's an issue of some sort. We need to find the issue, fix the issue, and then have a much better exception come out of this.

setUpClass (openstack.tests.functional.network.v2.test_floating_ip.TestFloatingIP)
----------------------------------------------------------------------------------

Captured traceback:
~~~~~~~~~~~~~~~~~~~
    Traceback (most recent call last):
      File "openstack/tests/functional/network/v2/test_floating_ip.py", line 46, in setUpClass
        net = cls._create_network(cls.EXT_NET_NAME, **args)
      File "openstack/tests/functional/network/v2/test_floating_ip.py", line 102, in _create_network
        net = cls.conn.network.create_network(name=name, **args)
      File "openstack/network/v2/_proxy.py", line 579, in create_network
        return self._create(network.Network, **attrs)
      File "openstack/proxy.py", line 176, in _create
        return res.create(self.session)
      File "openstack/resource.py", line 564, in create
        resp = self.create_by_id(session, self._attrs, self.id, path_args=self)
      File "openstack/resource.py", line 546, in create_by_id
        resp = session.post(url, endpoint_filter=cls.service, **args)
      File "/Users/brian/rackspace/openstack/python-openstacksdk/.tox/functional/lib/python2.7/site-packages/keystoneauth1/session.py", line 515, in post
        return self.request(url, 'POST', **kwargs)
      File "/Users/brian/rackspace/openstack/python-openstacksdk/.tox/functional/lib/python2.7/site-packages/keystoneauth1/_utils.py", line 180, in inner
        return func(*args, **kwargs)
      File "/Users/brian/rackspace/openstack/python-openstacksdk/.tox/functional/lib/python2.7/site-packages/keystoneauth1/session.py", line 410, in request
        raise exceptions.from_response(resp, method, url)
    keystoneauth1.exceptions.http.Conflict: Conflict (HTTP 409) (Request-ID: req-c424f9af-9146-48d7-8e62-50208cb79edf)

[Terry Howe (thowe-g)]

quota exceeded maybe although I'd expect something other than a 409 for that.

[Richard Theis (rtheis)]

This error is no longer seen in recent functional test runs.