Alex has added Tempest to this bug report for adding more log for the
investigation and that is done on
https://review.openstack.org/#/c/126908/
So this bug report should be close now.
** Changed in: tempest
Status: Confirmed => Fix Released
--
You received this bug notification because
** Changed in: neutron
Status: Fix Committed = Fix Released
** Changed in: neutron
Milestone: None = liberty-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1357055
Title:
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1357055
Title:
Race to delete shared subnet in Tempest neutron full
As I and Salvatore get same conclusions. This isn't bug neutron and
nova. It should be tempest bug. I removed nova from affected projects.
** No longer affects: nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
I came to the same conclusions as Alex: the servers are not deleted
hence the error.
However, the logging which Alex is claiming for is already there.
Indeed here are the delete operations on teardown for a failing test:
salvatore@trustillo:~$ cat tempest.txt.gz | grep -i
** Changed in: nova
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1357055
Title:
Race to delete shared subnet in Tempest neutron full jobs
yea, one more case.
I didn't the root cause. But put my analyze at here.
The analyze base on this:
http://logs.openstack.org/71/125171/2/gate/gate-tempest-dsvm-neutron-full/62dd074/console.html
The subnet is deleted at:
e-r query here: https://review.openstack.org/#/c/114359/
If this is mostly just neutron full jobs, this might make sense, i.e.
those run with tenant isolation so maybe there are multiple tests
running at the same time allocating ports on the same subnet and then
when one test completes and tries
8 matches
Mail list logo
