yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1539444@xxxxxxxxxxxxxxxxxx>]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
       Status: Incomplete => Expired

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

Title:
  router-interface-add on external network brings up external gateway ip

Status in neutron:
  Expired

Bug description:
  Having external provider/floating networks (router:external True), you
  normally attach them to you're router via: router-gateway-set. Which
  will add an ip address from the subnet allocation pool to the router
  namespace.

  But instead, when users do router-interface-add on that external
  network, the defined gateway_ip from the subnet is brought up in the
  namespace. Your floating network is instantly unavailable, because
  your networks gateway IP is running twice.

  The expected behavior for external networks, when (accidentally or
  because not known)  using router-interface-add on them, is to behave
  like router-gateway-set, or at least to deny that operation and
  definitely not bring up the gateway_ip defined in the subnet.

  Reproduce:

   neutron net-create --router:external [...]
   neutron subnet-create --gateway <external_gateway_ip> [...]
   neutron router-interface-add <router> <subnet>

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