yahoo-eng-team team mailing list archive

[Calvin Walton <calvin.walton@xxxxxxxxxx>]

Public bug reported:

I have Openstack Nova set up using nova-network in multi-host mode. I
wanted all instances to be able to resolve each-other via dns, so I
enabled update_dns_entries=True in nova.conf

Upon terminating an instance, I get the following traceback in nova-
compute.log on the compute node hosting the instance:

Traceback (most recent call last):

  File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 134, in _dispatch_and_reply
    incoming.message))

  File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 177, in _dispatch
    return self._do_dispatch(endpoint, method, ctxt, args)

  File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 123, in _do_dispatch
    result = getattr(endpoint, method)(ctxt, **new_args)

  File "/usr/lib/python2.7/dist-packages/nova/network/floating_ips.py", line 187, in deallocate_for_instance
    super(FloatingIP, self).deallocate_for_instance(context, **kwargs)

  File "/usr/lib/python2.7/dist-packages/nova/network/manager.py", line 568, in deallocate_for_instance
    network_ids = [fixed_ip.network_id for fixed_ip in fixed_ips]

AttributeError: 'str' object has no attribute 'network_id'

Some spelunking reveals that this was introduced in the following commit:
https://github.com/openstack/nova/commit/03d34c975586788dc25249b5e0b962fc0634008c
which changed the "fixed_ips" array to contain a list of string ip address, rather than fixed_ip objects, but neglected to update the code under the CONF.update_dns_entries branch below to match.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  nova-network with multi-host and update_dns_entries crashes during
  instance termination

Status in OpenStack Compute (Nova):
  New

Bug description:
  I have Openstack Nova set up using nova-network in multi-host mode. I
  wanted all instances to be able to resolve each-other via dns, so I
  enabled update_dns_entries=True in nova.conf

  Upon terminating an instance, I get the following traceback in nova-
  compute.log on the compute node hosting the instance:

  Traceback (most recent call last):

    File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 134, in _dispatch_and_reply
      incoming.message))

    File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 177, in _dispatch
      return self._do_dispatch(endpoint, method, ctxt, args)

    File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 123, in _do_dispatch
      result = getattr(endpoint, method)(ctxt, **new_args)

    File "/usr/lib/python2.7/dist-packages/nova/network/floating_ips.py", line 187, in deallocate_for_instance
      super(FloatingIP, self).deallocate_for_instance(context, **kwargs)

    File "/usr/lib/python2.7/dist-packages/nova/network/manager.py", line 568, in deallocate_for_instance
      network_ids = [fixed_ip.network_id for fixed_ip in fixed_ips]

  AttributeError: 'str' object has no attribute 'network_id'

  Some spelunking reveals that this was introduced in the following commit:
  https://github.com/openstack/nova/commit/03d34c975586788dc25249b5e0b962fc0634008c
  which changed the "fixed_ips" array to contain a list of string ip address, rather than fixed_ip objects, but neglected to update the code under the CONF.update_dns_entries branch below to match.

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