yahoo-eng-team team mailing list archive

[Rodolfo Alonso <1904436@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When a subnet is created using a subnet pool (--subnet-pool option), the
option --gateway is not honored.

According to [1][2], the gateway IP is read from the input parameters
only when --subnet-range is provided (subnet['cidr']).

It could be easy to, when a subnet pool is provided and a subnet range
is selected, to check if the provided gateway IP belongs to this subnet
range and assign it.


[1]https://github.com/openstack/neutron/blob/40c501dcb158b1ab14137c94c60697e19a73c170/neutron/db/ipam_pluggable_backend.py#L596-L602
[2]https://github.com/openstack/neutron/blob/40c501dcb158b1ab14137c94c60697e19a73c170/neutron/db/ipam_backend_mixin.py#L67

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  "gateway" option is not honored when creating a subnet with subnet
  pool

Status in neutron:
  New

Bug description:
  When a subnet is created using a subnet pool (--subnet-pool option),
  the option --gateway is not honored.

  According to [1][2], the gateway IP is read from the input parameters
  only when --subnet-range is provided (subnet['cidr']).

  It could be easy to, when a subnet pool is provided and a subnet range
  is selected, to check if the provided gateway IP belongs to this
  subnet range and assign it.

  
  [1]https://github.com/openstack/neutron/blob/40c501dcb158b1ab14137c94c60697e19a73c170/neutron/db/ipam_pluggable_backend.py#L596-L602
  [2]https://github.com/openstack/neutron/blob/40c501dcb158b1ab14137c94c60697e19a73c170/neutron/db/ipam_backend_mixin.py#L67

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