yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
       Status: Confirmed => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1350884

Title:
  IPv6 routes are not deleted in linux_net.py/ensure_bridge

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Using Nova-Network with use_ipv6 = True creates a problem. If an
  instance is spawned on a compute-node the br100 is created and the
  IPv4 routes are moved from the physical interface to the bridge. This
  does not seem to happen with the IPv6 routes.

  I end up with two routes for the same destination. One via the
  physical device and one via br100. This breaks the functionality until
  I delete the route that directs to the physical interface. As far as I
  can see in the linux_net.py#L1553 (stable/Icehouse) the "ip -6 route
  del" should be run along with ensure_bridge there.

  Also the interface should not accept RAs in the future since this
  would set the default route again.

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