nova-compute doesn't start if there is difference between current compute driver and driver which was used to create instance
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned | ||
nova-lxd |
Triaged
|
Low
|
Unassigned |
Bug Description
Steps to reproduce
==================
1. Create instance with (for example) qemu as nova-compute backend.
2. Change nova-compute backend to (for example) lxd.
3. Restart nova-compute service
Expected result
===============
I expected to see an error with something like this: "You have to delete all your instances, which were created with old nova-compute driver. Use 'openstack server delete instance-name' on your controller node."
Actual result
=============
nova-compute service doesn't start and there is no clear explanation in nova-compute.log (see log below).
Environment
===========
1. Version of OpenStack is Ocata:
user@compute ~> dpkg -l | grep nova
rc nova-api 2:15.0.
ii nova-common 2:15.0.
ii nova-compute 2:15.0.
rc nova-compute-kvm 2:15.0.
ii nova-compute-
ii nova-compute-lxd 15.0.2-
rc nova-conductor 2:15.0.
rc nova-consoleauth 2:15.0.
rc nova-novncproxy 2:15.0.
rc nova-placement-api 2:15.0.
rc nova-scheduler 2:15.0.
ii python-nova 2:15.0.
ii python-nova-lxd 15.0.2-
ii python-novaclient 2:7.1.0-
2. Hypervisors: qemu and lxd
3. Storage: lvm
4. Networking type: Neutron with OpenVSwitch
Log
==============
nova-compute.log:
2017-08-08 16:18:51.112 29592 INFO nova.service [-] Starting compute node (version 15.0.5)
2017-08-08 16:18:51.882 29592 INFO oslo.privsep.daemon [req-0777ab5e-
2017-08-08 16:18:53.810 29592 INFO oslo.privsep.daemon [req-0777ab5e-
2017-08-08 16:18:53.812 29592 INFO oslo.privsep.daemon [-] privsep daemon starting
2017-08-08 16:18:53.812 29592 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0
2017-08-08 16:18:53.813 29592 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_NET_
2017-08-08 16:18:53.813 29592 INFO oslo.privsep.daemon [-] privsep daemon running as pid 29634
2017-08-08 16:18:53.957 29592 INFO os_vif [req-0777ab5e-
2017-08-08 16:18:54.310 29592 INFO os_vif [req-0777ab5e-
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
2017-08-08 16:18:54.408 29592 ERROR oslo_service.
This is a bug in the nova-lxd driver code, which manages bugs through some other launchpad project.