← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1262563] [NEW] admin vm associate floating ip failed

 

Public bug reported:

Version: Stable/Havana
When an admin user in one tenant creates a VM in a network belongin different tenant,then admin  associating floating ip to that VM  will fail,because that tenant' network can't connect to router which belongs to the tenant admin is in.
the fail log in neutron is below:

Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/neutron/api/v2/resource.py", line 84, in resource
     result = method(request=request, **args)
   File "/usr/lib/python2.7/dist-packages/neutron/api/v2/base.py", line 486, in update
     obj = obj_updater(request.context, id, **kwargs)
   File "/usr/lib/python2.7/dist-packages/neutron/db/l3_db.py", line 661, in update_floatingip
     context.elevated(), fip_port_id))
   File "/usr/lib/python2.7/dist-packages/neutron/db/l3_db.py", line 582, in _update_fip_assoc
     floatingip_db['floating_network_id'])
   File "/usr/lib/python2.7/dist-packages/neutron/db/l3_db.py", line 556, in get_assoc_data
     floating_network_id)
   File "/usr/lib/python2.7/dist-packages/neutron/db/l3_db.py", line 492, in _get_router_for_floatingip
     port_id=internal_port['id'])
 ExternalGatewayForFloatingIPNotFound: External network c2ce01dc-e59e-463b-a860-b0ea69ef3535 is not reachable from subnet 6229560c-6ebf-40d4-a478-d67864360647.  Therefore, cannot associate Port 5b816263-0f96-4545-8b37-e4b4ced687af with a Floating IP.

** Affects: nova
     Importance: Undecided
     Assignee: shihanzhang (shihanzhang)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => shihanzhang (shihanzhang)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1262563

Title:
  admin vm associate floating ip failed

Status in OpenStack Compute (Nova):
  New

Bug description:
  Version: Stable/Havana
  When an admin user in one tenant creates a VM in a network belongin different tenant,then admin  associating floating ip to that VM  will fail,because that tenant' network can't connect to router which belongs to the tenant admin is in.
  the fail log in neutron is below:

  Traceback (most recent call last):
     File "/usr/lib/python2.7/dist-packages/neutron/api/v2/resource.py", line 84, in resource
       result = method(request=request, **args)
     File "/usr/lib/python2.7/dist-packages/neutron/api/v2/base.py", line 486, in update
       obj = obj_updater(request.context, id, **kwargs)
     File "/usr/lib/python2.7/dist-packages/neutron/db/l3_db.py", line 661, in update_floatingip
       context.elevated(), fip_port_id))
     File "/usr/lib/python2.7/dist-packages/neutron/db/l3_db.py", line 582, in _update_fip_assoc
       floatingip_db['floating_network_id'])
     File "/usr/lib/python2.7/dist-packages/neutron/db/l3_db.py", line 556, in get_assoc_data
       floating_network_id)
     File "/usr/lib/python2.7/dist-packages/neutron/db/l3_db.py", line 492, in _get_router_for_floatingip
       port_id=internal_port['id'])
   ExternalGatewayForFloatingIPNotFound: External network c2ce01dc-e59e-463b-a860-b0ea69ef3535 is not reachable from subnet 6229560c-6ebf-40d4-a478-d67864360647.  Therefore, cannot associate Port 5b816263-0f96-4545-8b37-e4b4ced687af with a Floating IP.

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


Follow ups

References