yahoo-eng-team team mailing list archive

[Chuck Short <chuck.short@xxxxxxxxxxxxx>]

** Also affects: neutron/juno
   Importance: Undecided
       Status: New

** Changed in: neutron/juno
    Milestone: None => 2014.2.2

** Changed in: neutron/juno
       Status: New => Fix Committed

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

Title:
  SLAAC IPv6 addressing doesn't work with more than one subnet

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

Bug description:
  When network has more than one IPv6 SLAAC (or dhcp-stateless) subnets,
  the port receives SLAAC address only from first one, the second
  address is from fixed IPs range.

  Scenario:
  1) create a network and two SLAAC subnets:
  ~$ neutron net-create net12
  ~$ neutron subnet-create net12 --ipv6-ra-mode=slaac --ipv6-address-mode=slaac --ip-version=6 2003::/64
  | allocation_pools  | {"start": "2003::2", "end": "2003::ffff:ffff:ffff:fffe"} |
  | cidr              | 2003::/64                                                |
  | dns_nameservers   |                                                          |
  | enable_dhcp       | True                                                     |
  | gateway_ip        | 2003::1                                                  |
  | host_routes       |                                                          |
  | id                | 220b7e4e-b30a-4d5c-847d-58df72bf7e8d                     |
  | ip_version        | 6                                                        |
  | ipv6_address_mode | slaac                                                    |
  | ipv6_ra_mode      | slaac                                                    |
  | name              |                                                          |
  | network_id        | 4cfe1699-a10d-4706-bedb-5680cb5cf27f                     |
  | tenant_id         | 834b2e7732cb4ad4b3df81fe0b0ea906                         |

  ~$ neutron subnet-create --name=additional net12 --ipv6-ra-mode=slaac --ipv6-address-mode=slaac --ip-version=6 2004::/64
  | allocation_pools  | {"start": "2004::2", "end": "2004::ffff:ffff:ffff:fffe"} |
  | cidr              | 2004::/64                                                |
  | dns_nameservers   |                                                          |
  | enable_dhcp       | True                                                     |
  | gateway_ip        | 2004::1                                                  |
  | host_routes       |                                                          |
  | id                | e48e5d96-565f-45b1-8efc-4634d3ed8bf8                     |
  | ip_version        | 6                                                        |
  | ipv6_address_mode | slaac                                                    |
  | ipv6_ra_mode      | slaac                                                    |
  | name              | additional                                               |
  | network_id        | 4cfe1699-a10d-4706-bedb-5680cb5cf27f                     |
  | tenant_id         | 834b2e7732cb4ad4b3df81fe0b0ea906                         |

  Now let's create port in this network:

  ~$ neutron port-create net12
  Created a new port:
  +-----------------------+--------------------------------------------------------------------------------------------------+
  | Field                 | Value                                                                                            |
  +-----------------------+--------------------------------------------------------------------------------------------------+
  | admin_state_up        | True                                                                                             |
  | allowed_address_pairs |                                                                                                  |
  | binding:vnic_type     | normal                                                                                           |
  | device_id             |                                                                                                  |
  | device_owner          |                                                                                                  |
  | fixed_ips             | {"subnet_id": "220b7e4e-b30a-4d5c-847d-58df72bf7e8d", "ip_address": "2003::f816:3eff:fe55:6297"} |
  |                       | {"subnet_id": "e48e5d96-565f-45b1-8efc-4634d3ed8bf8", "ip_address": "2004::2"}                   |
  | id                    | 12c29fd4-1c68-4aea-88c6-b89d73ebac2c                                                             |
  | mac_address           | fa:16:3e:55:62:97                                                                                |
  | name                  |                                                                                                  |
  | network_id            | 4cfe1699-a10d-4706-bedb-5680cb5cf27f                                                             |
  | security_groups       | 65e77cc0-879c-4ed0-b647-d27d36844e0b                                                             |
  | status                | DOWN                                                                                             |
  | tenant_id             | 834b2e7732cb4ad4b3df81fe0b0ea906                                                                 |

  As we see we get SLAAC IP from first subnet and fixed IP from second one.
  Expected is to get SLAAC IPs from both subnets.

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