Race in deleting ports during Tempest Runs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Confirmed
|
Critical
|
Unassigned |
Bug Description
This is similar to https:/
When trying to tear down subnets, they sometimes fail because the port still exists. However there is no indication that the port delete failed.
2017-06-05 18:38:20.846777 | Captured traceback-1:
2017-06-05 18:38:20.846795 | ~~~~~~~
2017-06-05 18:38:20.846817 | Traceback (most recent call last):
2017-06-05 18:38:20.846853 | File "tempest/
2017-06-05 18:38:20.846890 | return func(*args, **kwargs)
2017-06-05 18:38:20.846926 | File "tempest/
2017-06-05 18:38:20.846949 | return self.delete_
2017-06-05 18:38:20.846981 | File "tempest/
2017-06-05 18:38:20.847004 | resp, body = self.delete(
2017-06-05 18:38:20.847034 | File "tempest/
2017-06-05 18:38:20.847064 | return self.request(
2017-06-05 18:38:20.847094 | File "tempest/
2017-06-05 18:38:20.847117 | self._error_
2017-06-05 18:38:20.847149 | File "tempest/
2017-06-05 18:38:20.847175 | raise exceptions.
2017-06-05 18:38:20.847208 | tempest.
2017-06-05 18:38:20.847274 | Details: {u'detail': u'', u'message': u'Unable to complete operation on subnet 276de24c-
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
32 hits for 24h :(
http:// logstash. openstack. org/#dashboard/ file/logstash. json?query= message% 3A%5C%22One% 20or%20more% 20ports% 20have% 20an%20IP% 20allocation% 20from% 20this% 20subnet% 5C%22%20AND% 20filename% 3A%20%5C% 22console. html%5C% 22%20AND% 20build_ name%3A% 20%5C%22gate- tempest- dsvm-neutron- linuxbridge- ubuntu- xenial% 5C%22