Public bug reported:
After performing a package update of a deployed Folsom cloud (with
running instances), nova-compute fails to start up with the following
trace back:
2013-03-21 18:39:56.485 17998 INFO nova.manager [-] Skipping periodic task
_periodic_update_dns because its interval is negative
2013-03-21 18:39:56.624 INFO nova.openstack.common.rpc.common
[req-3bfe62c1-f6b1-4bc5-b0d7-38c498fc56b9 None None] Connected to AMQP server
on test-07.os.magners.qa.lexington:5672
2013-03-21 18:39:56.658 17998 AUDIT nova.service [-] Starting compute node
(version 2013.1)
2013-03-21 18:39:57.287 17998 CRITICAL nova [-] vif_type parameter must be
present for this vif_driver implementation
2013-03-21 18:39:57.287 17998 TRACE nova Traceback (most recent call last):
2013-03-21 18:39:57.287 17998 TRACE nova File "/usr/bin/nova-compute", line
85, in <module>
2013-03-21 18:39:57.287 17998 TRACE nova service.wait()
2013-03-21 18:39:57.287 17998 TRACE nova File
"/usr/lib/python2.7/dist-packages/nova/service.py", line 689, in wait
2013-03-21 18:39:57.287 17998 TRACE nova _launcher.wait()
2013-03-21 18:39:57.287 17998 TRACE nova File
"/usr/lib/python2.7/dist-packages/nova/service.py", line 209, in wait
2013-03-21 18:39:57.287 17998 TRACE nova super(ServiceLauncher, self).wait()
2013-03-21 18:39:57.287 17998 TRACE nova File
"/usr/lib/python2.7/dist-packages/nova/service.py", line 179, in wait
2013-03-21 18:39:57.287 17998 TRACE nova service.wait()
2013-03-21 18:39:57.287 17998 TRACE nova File
"/usr/lib/python2.7/dist-packages/eventlet/greenthread.py", line 166, in wait
2013-03-21 18:39:57.287 17998 TRACE nova return self._exit_event.wait()
2013-03-21 18:39:57.287 17998 TRACE nova File
"/usr/lib/python2.7/dist-packages/eventlet/event.py", line 116, in wait
2013-03-21 18:39:57.287 17998 TRACE nova return hubs.get_hub().switch()
2013-03-21 18:39:57.287 17998 TRACE nova File
"/usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line 177, in switch
2013-03-21 18:39:57.287 17998 TRACE nova return self.greenlet.switch()
2013-03-21 18:39:57.287 17998 TRACE nova File
"/usr/lib/python2.7/dist-packages/eventlet/greenthread.py", line 192, in main
2013-03-21 18:39:57.287 17998 TRACE nova result = function(*args, **kwargs)
2013-03-21 18:39:57.287 17998 TRACE nova File
"/usr/lib/python2.7/dist-packages/nova/service.py", line 147, in run_server
2013-03-21 18:39:57.287 17998 TRACE nova server.start()
2013-03-21 18:39:57.287 17998 TRACE nova File
"/usr/lib/python2.7/dist-packages/nova/service.py", line 429, in start
2013-03-21 18:39:57.287 17998 TRACE nova self.manager.init_host()
2013-03-21 18:39:57.287 17998 TRACE nova File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 574, in
init_host
2013-03-21 18:39:57.287 17998 TRACE nova self._init_instance(context,
instance)
2013-03-21 18:39:57.287 17998 TRACE nova File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 463, in
_init_instance
2013-03-21 18:39:57.287 17998 TRACE nova self.driver.plug_vifs(instance,
legacy_net_info)
2013-03-21 18:39:57.287 17998 TRACE nova File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 686, in
plug_vifs
2013-03-21 18:39:57.287 17998 TRACE nova self.vif_driver.plug(instance,
(network, mapping))
2013-03-21 18:39:57.287 17998 TRACE nova File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 391, in plug
2013-03-21 18:39:57.287 17998 TRACE nova _("vif_type parameter must be
present "
2013-03-21 18:39:57.287 17998 TRACE nova NovaException: vif_type parameter must
be present for this vif_driver implementation
2013-03-21 18:39:57.287 17998 TRACE nova
2013-03-21 18:40:56.446 18678 INFO nova.virt.driver [-] Loading compute driver
'libvirt.LibvirtDriver'
2013-03-21 18:40:56.491 18678 INFO nova.manager [-] Skipping periodic task
_periodic_update_dns because its interval is negative
This is a nova-network multi_host/libvirt deployment.
nova.conf on the compute node is as follows:
[DEFAULT]
dhcpbridge_flagfile=/etc/nova/nova.conf
dhcpbridge=/usr/bin/nova-dhcpbridge
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
force_dhcp_release=True
iscsi_helper=tgtadm
libvirt_use_virtio_for_bridges=True
connection_type=libvirt
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf
verbose=True
ec2_private_dns_show_ip=True
api_paste_config=/etc/nova/api-paste.ini
volumes_path=/var/lib/nova/volumes
auth_strategy=keystone
auto_assign_floating_ip=True
sql_connection=mysql://nova:@XXX/nova
rabbit_host=test-07.os.magners.qa.lexington
rabbit_userid=nova
rabbit_password=XXX
rabbit_virtual_host=nova
glance_api_servers=http://test-08.os.magners.qa.lexington:9292
network_manager=nova.network.manager.FlatDHCPManager
flat_interface=eth1
ec2_dmz_host=test-02.os.magners.qa.lexington
volume_api_class=nova.volume.cinder.API
rbd_user=nova-compute
rbd_secret_uuid=514c9fca-8cbe-11e2-9c52-3bc8c7819472
rbd_pool=nova
This could very well be a config issue, in which case its a packaging
bug, or perhaps a data migration. I know there has been work this cycle
around the libvirt interface drivers
(https://review.openstack.org/#/c/20244/)
** Affects: nova
Importance: Undecided
Status: New
** Affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Tags: upgrade
** Also affects: nova
Importance: Undecided
Status: New
** Tags added: upgrade
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1158561
Title:
After upgrade, nova-compute fails to start: vif_parameter must be
present.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1158561/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
