yahoo-eng-team team mailing list archive

[Andrew Boik <dboik@xxxxxxxxx>]

Public bug reported:

Performing a port-update with a different set of fixed-ips than are
currently on the port will be reported as a success by Neutron, however
the actual addresses will not be updated in the Linux network namespace.
This now has more functional implications as a result of multiple
subnets being allowed on the external router interface
(https://review.openstack.org/#/c/149068). If the interface has two
subnets and the user wishes to remove one, they will have to clear the
gateway interface first, removing both (causing traffic disruption),
delete the subnet, and re-set the gateway on the router to re-add the
remaining subnet. If port-update were functional for router addresses,
this command could be used to remove a second subnet without causing
disruption to the first.

** Affects: neutron
     Importance: Undecided
     Assignee: Andrew Boik (drewboik)
         Status: New


** Tags: ipv6

** Changed in: neutron
     Assignee: (unassigned) => Andrew Boik (drewboik)

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

Title:
  port-update --fixed-ips doesn't work for routers

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Performing a port-update with a different set of fixed-ips than are
  currently on the port will be reported as a success by Neutron,
  however the actual addresses will not be updated in the Linux network
  namespace. This now has more functional implications as a result of
  multiple subnets being allowed on the external router interface
  (https://review.openstack.org/#/c/149068). If the interface has two
  subnets and the user wishes to remove one, they will have to clear the
  gateway interface first, removing both (causing traffic disruption),
  delete the subnet, and re-set the gateway on the router to re-add the
  remaining subnet. If port-update were functional for router addresses,
  this command could be used to remove a second subnet without causing
  disruption to the first.

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