yahoo-eng-team team mailing list archive

[John Davidge <jodavidg@xxxxxxxxx>]

Let's put this on hold until we can discuss further at the summit. In
the meantime we can fix the devstack failures when a default subnetpool
is set https://bugs.launchpad.net/devstack/+bug/1472200

** Changed in: neutron
       Status: In Progress => Opinion

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

Title:
  _get_subnetpool_id does not return None when a cidr is specified and a
  subnetpool_id isn't.

Status in neutron:
  Opinion

Bug description:
  I've just noticed this while rebasing the ongoing prefix delegation
  patch to align with the changes made by:
  https://review.openstack.org/#/c/197090/

  When (https://review.openstack.org/#/c/168098/) was merged, it was
  decided that to get the old behaviour the user would have to
  explicitly specify "None" as the subnetpool_id when creating a subnet.
  I'm not sure this was the correct choice, as this breaks legacy
  applications using the neutron API.

  This can be seen by simply running devstack with a value set for
  default_ipv4_subnet_pool and/or default_ipv6_subnet_pool.

  To recreate in devstack:

  1. Set default_ipv4_subnet_pool and/or default_ipv6_subnet_pool in /opt/stack/neutron/etc/neutron.conf to any value other than None, e.g default_ipv6_subnet_pool = "prefix_delegation"
  2. Run the ./stack.sh script with ip_version set appropriately for the defaults set above. It will fail when trying to create the default networks.

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