yahoo-eng-team team mailing list archive

[John Kasperski <jckasper@xxxxxxxxxx>]

Public bug reported:

There are three variations here with the subnet-update command:

1) subnet-update of the gateway_ip  such that the new gateway is placed
in the existing subnet allocaton pool.  This results in
GatewayConflictWithAllocationPools.

2) subnet-update of both the gateway_ip and the allocation_poll .  If
the new gateway IP is located in the new allocation pool, then
GatewayConflictWithAllocationPools is returned.

3) subnet-update of just the allocation_pool.  If the new allocation
pool includes the existing gateway_ip, no error is returned.

Scenario 3 needs to be fixed to return same exception as (1) and (2).

** Affects: neutron
     Importance: Undecided
     Assignee: John Kasperski (jckasper)
         Status: In Progress

** Changed in: neutron
     Assignee: (unassigned) => John Kasperski (jckasper)

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

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

Title:
  subnet-update of allocation_pool does not prevent overlap of existing
  gateway IP

Status in neutron:
  In Progress

Bug description:
  There are three variations here with the subnet-update command:

  1) subnet-update of the gateway_ip  such that the new gateway is
  placed in the existing subnet allocaton pool.  This results in
  GatewayConflictWithAllocationPools.

  2) subnet-update of both the gateway_ip and the allocation_poll .  If
  the new gateway IP is located in the new allocation pool, then
  GatewayConflictWithAllocationPools is returned.

  3) subnet-update of just the allocation_pool.  If the new allocation
  pool includes the existing gateway_ip, no error is returned.

  Scenario 3 needs to be fixed to return same exception as (1) and (2).

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