security group listing race
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Critical
|
Aaron Rosen | ||
Icehouse |
Fix Released
|
Critical
|
Sean Dague |
Bug Description
In this grenade job
http://
One process tries to list ALL security groups :
"2013-12-19 06:42:11.519 15319 INFO tempest.
(pid=15319)
While another process deletes one:
http://
"2013-12-19 06:42:11.510 15315 INFO tempest.
(pid=15315)
The test case failed on listing ALL security group request , which requested closely in time to a security group deletion.
'<message>Security group 27 not found.<
$ nova secgroup-list --all-tenants 1 # is the cli equivalent of the failing request, this call should not fail with 'Security group 27 not found.'
tags: | added: network |
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in nova: | |
assignee: | nobody → Aaron Rosen (arosen) |
tags: | removed: in-stable-icehouse |
Changed in nova: | |
milestone: | none → juno-1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | juno-1 → 2014.2 |
Is this with Neutron or traditional nova networks?
Thanks
Gary