yahoo-eng-team team mailing list archive

[Slawek Kaplonski <1938788@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Currently when new port is created with fixed_ip given, neutron is not
validating if that fixed_ip address isn't the same as subnet's gateway
IP. That may cause problems, like e.g.:

$ openstack subnet show <subnet-id>
| allocation_pools  | 10.0.0.2-10.0.0.254
| cidr              | 10.0.0.0/24   
| enable_dhcp       | True  
...
| gateway_ip        | 10.0.0.1  


$ nova boot   --flavor test --image test  --nic  net-id=<network-id>,v4-fixed-ip=10.0.0.1  test-vm1

The instance will be created successfully, but after that, network
communication issue could be happened since the gateway ip conflict.

So Neutron should forbid creation of the port with gateway's ip address
if it is not router's port (device_owner isn't set for one of the router
device owners).

** Affects: neutron
     Importance: Undecided
     Assignee: Slawek Kaplonski (slaweq)
         Status: Triaged


** Tags: l3-ipam-dhcp

** Changed in: neutron
     Assignee: (unassigned) => Slawek Kaplonski (slaweq)

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

** Tags added: l3-ipam-dhcp

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

Title:
  Validate if fixed_ip given for port isn't the same as subnet's
  gateway_ip

Status in neutron:
  Triaged

Bug description:
  Currently when new port is created with fixed_ip given, neutron is not
  validating if that fixed_ip address isn't the same as subnet's gateway
  IP. That may cause problems, like e.g.:

  $ openstack subnet show <subnet-id>
  | allocation_pools  | 10.0.0.2-10.0.0.254
  | cidr              | 10.0.0.0/24   
  | enable_dhcp       | True  
  ...
  | gateway_ip        | 10.0.0.1  

  
  $ nova boot   --flavor test --image test  --nic  net-id=<network-id>,v4-fixed-ip=10.0.0.1  test-vm1

  The instance will be created successfully, but after that, network
  communication issue could be happened since the gateway ip conflict.

  So Neutron should forbid creation of the port with gateway's ip
  address if it is not router's port (device_owner isn't set for one of
  the router device owners).

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