yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1250105@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/1250105

Title:
  Cannot assign a floating IP to an instance that is reachable by an
  extra route

Status in neutron:
  Expired

Bug description:
  Consider the following network topology:

  Public network --- router1 --- [multi-homed-instance]--- [internal-
  instance]

  In this topology, we have:
  - a public network
  - a router (router1)
  - an intermediate network (and a subnet)
  - an internal network (and a subnet)
  - a multi-homed instance with ports on both the intermediate network and the internal network
  - an internal-instance with a port connected to the internal network

  We are trying to create a network topology in which traffic to/from
  the internal network must go through the multi-homed-instance for
  security and other reasons.

  For the sake of this example we will use the following addresses:
  - Public network: 172.24.4.0/24
  - Intermediate subnet: 10.1.0.0/24
  - Internal subnet: 10.2.0.0/24
  - Router: 172.24.4.226 (public), 10.1.0.1 (intermediate)
  - multi-homed-instance: 10.1.0.10 (intermediate), 10.2.0.10 (internal)
  - internal-instance: 10.2.0.81 (internal)

  The default route on the internal subnet is set to 10.2.0.10 (the
  multi-homed-instance)

  Using the extra route extension, the router is configured to route all traffic to 10.2.0.0/24 through 10.1.0.10:
  neutron router-update router --routes type=dict list=true nexthop=10.1.0.10,destination=10.2.0.0/24

  When trying to allocate a floating IP address and assign it to the internal host, we get an exception:
  404-{u'NeutronError': {u'message': u'External network a470bb7f-e06d-4214-a1bb-a8ec7727db23 is not reachable from subnet 10b47bbd-4ae4-4dbf-98ce-3f5bb9d7a081.  Therefore, cannot associate Port 75cddce2-f865-45e9-99c5-8a0a6902ecfc with a Floating IP.', u'type': u'ExternalGatewayForFloatingIPNotFound', u'detail': u''}}

  
  The attached script can be used to recreate this bug.

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