nova-network with multi-host and update_dns_entries crashes during instance termination
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Davanum Srinivas (DIMS) |
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_
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/
incoming.
File "/usr/lib/
return self._do_
File "/usr/lib/
result = getattr(endpoint, method)(ctxt, **new_args)
File "/usr/lib/
super(
File "/usr/lib/
network_ids = [fixed_
AttributeError: 'str' object has no attribute 'network_id'
Some spelunking reveals that this was introduced in the following commit:
https:/
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_
Changed in nova: | |
importance: | Undecided → Low |
tags: | added: juno-backport-potential |
Changed in nova: | |
milestone: | none → kilo-rc1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | kilo-rc1 → 2015.1.0 |
A bit of further details - this is using the Ubuntu packages for Openstack juno on Ubuntu 14.04; the network type being used is FlatDHCPManager.