yahoo-eng-team team mailing list archive

[Armando Migliaccio <1358554@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

This happens on master and appears to be a regression of
https://review.openstack.org/#/c/112465/

Steps to reproduce:

- Deploy devstack with DVR *ON*
- Run tempest test test_volume_boot_pattern (more details available in [1])
- Watch the test fail

Once change 112465 is reverted, the test will be successful.


This does not imply that the change is at fault, instead, that another failure mode has been unveiled.

In fact, prior to change 112465, call [2] was made with the wrong agent
id, which caused the delete_port operation to abort altogether; this is
wrong and addressed in 112465. However, the boot from volume test, and
its sequence of operations revealed that the clean-up logic is not
working as it should.


[1] - https://github.com/openstack/tempest/blob/master/tempest/scenario/test_volume_boot_pattern.py#L31
[2] - https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/plugin.py#L1029

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: l3-dvr-backlog

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1358554

Title:
  test_volume_boot_pattern fails with DVR routers

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  This happens on master and appears to be a regression of
  https://review.openstack.org/#/c/112465/

  Steps to reproduce:

  - Deploy devstack with DVR *ON*
  - Run tempest test test_volume_boot_pattern (more details available in [1])
  - Watch the test fail

  Once change 112465 is reverted, the test will be successful.

  
  This does not imply that the change is at fault, instead, that another failure mode has been unveiled.

  In fact, prior to change 112465, call [2] was made with the wrong
  agent id, which caused the delete_port operation to abort altogether;
  this is wrong and addressed in 112465. However, the boot from volume
  test, and its sequence of operations revealed that the clean-up logic
  is not working as it should.

  
  [1] - https://github.com/openstack/tempest/blob/master/tempest/scenario/test_volume_boot_pattern.py#L31
  [2] - https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/plugin.py#L1029

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1358554/+subscriptions