yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: neutron
       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/1382076

Title:
  Can not add router interface to SLAAC network

Status in OpenStack Neutron (virtual network service):
  Fix Released
Status in neutron juno series:
  Fix Released

Bug description:
  Looks like after resolving of
  https://bugs.launchpad.net/neutron/+bug/1330826 it's impossible now to
  connect router to subnet with SLAAC addressing.

  Steps to reproduce:

  $ neutron net-create netto
  $ neutron subnet-create --ip_version 6 --ipv6-address-mode slaac --ipv6-ra-mode slaac netto 2021::/64
  $ neutron router-create netrouter
  $ neutron router-interface-add {router_id} {subnet_id}

  The error is:
  Invalid input for operation: IPv6 address 2021::1 can not be directly assigned to a port on subnet 8cc737a7-bac1-4fbc-b03d-dfdac7194c08 with slaac address mode.

  ** The same behaviour if you set gateway explicitly to fixed IP address like 2022::7:
  $ neutron subnet-create --ip_version 6 --gateway 2022::7 --ipv6-address-mode slaac --ipv6-ra-mode slaac netto 2022::/64
  $ neutron router-interface-add  {router_id} {subnet_id}
  Invalid input for operation: IPv6 address 2022::7 can not be directly assigned to a port on subnet f4ebf914-9749-49e4-9498-5c10c7bf9a5d with slaac address mode.

  *** The same behaviour if we use dhcpv6-stateless instead of SLAAC.

  1. It should be legal possibility to add port with fixed IP to SLAAC/stateless networks.
  2. When router add its interface to SLAAC subnet it should receive its own SLAAC address by default, if fixed IP address is not specified explicitly.

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