← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1197573] Re: nova interface-attach doesn't work with quantum when port|network|fixed id is omitted

 

Long incomplete bug with no response

** Changed in: nova
       Status: Incomplete => Invalid

-- 
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/1197573

Title:
  nova interface-attach doesn't work with quantum when
  port|network|fixed id is omitted

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  I am using the latest quantum and nova.  I am running tempest against
  it and the
  empest.api.compute.servers.test_attach_interfaces:AttachInterfacesTestJSON.test_create_list_show_delete_interfaces
  test fails.

  Tempest shows that it is making the request to attach the interface
  with no args ({"interfaceAttachment": {}})

  tempest.common.rest_client: INFO: Request: POST http://nova-controller.example.com:8774/v2/tempest/servers/40adfdf0-06f6-4da2-ac5b-41991d0c416a/os-interface
  tempest.common.rest_client: DEBUG: Request Headers: {'Content-Type': 'application/json', 'Accept': 'application/json', 'X-Auth-Token': '<Token omitted>'}
  tempest.common.rest_client: DEBUG: Request Body: {"interfaceAttachment": {}}

  
  When it does that I see this in the nova-compute log  (The below paste is also available in a readable format at http://paste.openstack.org/show/39535/)

  
  Traceback (most recent call last):
    File "/usr/local/csi/share/csi-nova.venv/lib/python2.6/site-packages/nova/network/api.py", line 84, in update_instance_cache_with_nw_info
      cache)
    File "/usr/local/csi/share/csi-nova.venv/lib/python2.6/site-packages/nova/db/api.py", line 818, in instance_info_cache_update
      return IMPL.instance_info_cache_update(context, instance_uuid, values)
    File "/usr/local/csi/share/csi-nova.venv/lib/python2.6/site-packages/nova/cmd/compute.py", line 50, in __call__
      raise exception.DBNotAllowed('nova-compute')
  DBNotAllowed: nova-compute
  2013-07-03 01:00:50,847 (nova.compute.manager): ERROR manager attach_interface allocate_port_for_instance returned 3 ports
  2013-07-03 01:00:50,848 (nova.openstack.common.rpc.amqp): ERROR amqp _process_data Exception during message handling
  Traceback (most recent call last):
    File "/usr/local/csi/share/csi-nova.venv/lib/python2.6/site-packages/nova/openstack/common/rpc/amqp.py", line 433, in _process_data
      **args)
    File "/usr/local/csi/share/csi-nova.venv/lib/python2.6/site-packages/nova/openstack/common/rpc/dispatcher.py", line 172, in dispatch
      result = getattr(proxyobj, method)(ctxt, **kwargs)
    File "/usr/local/csi/share/csi-nova.venv/lib/python2.6/site-packages/nova/compute/manager.py", line 3262, in attach_interface
      raise exception.InterfaceAttachFailed(instance=instance)

  Note that I have quantum configured with three networks.  When tempest
  creates an instance it does not specify a network so quantum creates
  an interface on all three networks.

  It is not clear to me what the expected behavior is when
  interfaceAttachment is equal to {}.

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