yahoo-eng-team team mailing list archive

[Rodolfo Alonso <1980339@xxxxxxxxxxxxxxxxxx>]

Sorry, I was wrong. The IPv6 address can be assigned (in other system).
It's this particular environment that doesn't allow to set any IPv6
address in an interface inside a namespace (disable_ipv6=0, so it could
be possible).

I'll close this bug.

** Changed in: neutron
       Status: New => Invalid

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

Title:
  [DHCP] IPv6 metadata address fails when it's added to the interface

Status in neutron:
  Invalid

Bug description:
  Bugzilla reference:
  https://bugzilla.redhat.com/show_bug.cgi?id=2102211

  
  Since [1] we can have IPv6 metadata. This is served via a link local address defined in neutron-lib [2].

  However the DHCP agent is adding this IPv6 address to the DHCP
  namespace using scope=global. Log [3] (NOTE: the first line of this
  log is an extra debug line added to print the "add_ip_address"
  parameters passed). In order to make this work, we should check the
  IPv6 scope and pass it to the method.

  [1]https://review.opendev.org/c/openstack/neutron/+/715482
  [2]https://github.com/openstack/neutron-lib/blob/c8132ff1b06b0d9c50faa19d30f0346cb6a2eea9/neutron_lib/constants.py#L627
  [3]https://paste.opendev.org/show/bjBibJe38eEGKdHdDn2y/

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