yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #56553
[Bug 1623691] Re: security group in use conflict during test cleanup
It looks like port deletion (as a consequence of server deletion) is
racing with the deletion of the default security group. This most likely
happens if Nova does not ensure that the port is indeed gone before
assuming that the server is indeed deleted.
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: tempest
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1623691
Title:
security group in use conflict during test cleanup
Status in neutron:
New
Status in OpenStack Compute (nova):
New
Status in tempest:
Invalid
Bug description:
ft12.1: tearDownClass (tempest.api.volume.test_volumes_actions.VolumesV1ActionsTest)_StringException: Traceback (most recent call last):
File "tempest/test.py", line 312, in tearDownClass
six.reraise(etype, value, trace)
File "tempest/test.py", line 295, in tearDownClass
teardown()
File "tempest/test.py", line 547, in clear_credentials
cls._creds_provider.clear_creds()
File "tempest/common/dynamic_creds.py", line 411, in clear_creds
self._cleanup_default_secgroup(creds.tenant_id)
File "tempest/common/dynamic_creds.py", line 358, in _cleanup_default_secgroup
nsg_client.delete_security_group(secgroup['id'])
File "tempest/lib/services/network/security_groups_client.py", line 58, in delete_security_group
return self.delete_resource(uri)
File "tempest/lib/services/network/base.py", line 41, in delete_resource
resp, body = self.delete(req_uri)
File "tempest/lib/common/rest_client.py", line 307, in delete
return self.request('DELETE', url, extra_headers, headers, body)
File "tempest/lib/common/rest_client.py", line 665, in request
resp, resp_body)
File "tempest/lib/common/rest_client.py", line 778, in _error_checker
raise exceptions.Conflict(resp_body, resp=resp)
tempest.lib.exceptions.Conflict: An object with that identifier already exists
Details: {u'type': u'SecurityGroupInUse', u'message': u'Security Group 73bda5d7-e097-4f16-a6ae-96f314c7e885 in use.', u'detail': u''}
It looks like the request to delete a security group is processed
before the request to delete the port using it and thus the conflict:
http://logs.openstack.org/77/346377/14/check/gate-grenade-dsvm-
neutron-dvr-
multinode/056b1cf/logs/new/screen-q-svc.txt.gz#_2016-09-14_20_51_33_845
http://logs.openstack.org/77/346377/14/check/gate-grenade-dsvm-
neutron-dvr-
multinode/056b1cf/logs/new/screen-q-svc.txt.gz#_2016-09-14_20_51_34_337
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1623691/+subscriptions
References