yahoo-eng-team team mailing list archive

[OpenStack Infra <1693771@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/468361
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1e9aca11b9736993e39972a36ecd53765f4b580a
Submitter: Jenkins
Branch:    master

commit 1e9aca11b9736993e39972a36ecd53765f4b580a
Author: Jens Rosenboom <j.rosenboom@xxxxxxxx>
Date:   Fri May 26 11:02:05 2017 +0000

    Fix security group rules created for dhcpv6
    
    In [1] the setup of security group rules for DHCP was refactored.
    However it assumed that DHCPv6 responses would go to the target IP,
    instead the destination will be the link-local address of the instance,
    so we will need to add this to the list of allowed destinations.
    
    [1] Ibfbf011284cbde396f74db9d982993f994082731
    
    Change-Id: I6bd24a98d7c72a1bac28999eb3c9a831ab2ab9bf
    Closes-Bug: 1693771


** Changed in: neutron
       Status: In Progress => 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/1693771

Title:
  Instance fails to receive DHCPv6 responses

Status in neutron:
  Fix Released

Bug description:
  When running an instance on a network with ipv6-address-mode
  dhcpv6-stateful, the instance fails to receive responses from the DHCP
  server. The workaround is to add an explicit security group rule
  allowing

  --proto udp --dst-port 546 --ethertype IPv6

  and then the DHCP handshake succeeds successfully.

  See https://review.openstack.org/#/c/386525/ and the failures at e.g.
  http://logs.openstack.org/25/386525/8/check/gate-tempest-dsvm-neutron-
  full-ssh/b4c7bf0/, the same setup worked fine in December, so this
  seems to be a regression introduced since then.

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