Open Stack

Hi,

We’re setting up 4 new compute nodes in our openstack Pike setup and 2 of them are behaving strangely, despite having the same hardware as the others. When I try to create a new instance on these compute nodes, the instance fail to spawn and the following error message appears in the log :

2019-05-24 15:13:35.559 16944 ERROR nova.compute.manager  Traceback (most recent call last):
2019-05-24 15:13:35.559 16944 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2203, in _build_resources
2019-05-24 15:13:35.559 16944 ERROR nova.compute.manager    yield resources
2019-05-24 15:13:35.559 16944 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2018, in _build_and_run_instance
2019-05-24 15:13:35.559 16944 ERROR nova.compute.manager     block_device_info=block_device_info)
2019-05-24 15:13:35.559 16944 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2898, in spawn
2019-05-24 15:13:35.559 16944 ERROR nova.compute.manager     block_device_info=block_device_info)
2019-05-24 15:13:35.559 16944 ERROR nova.compute.manager    File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 5220, in _get_guest_xml
2019-05-24 15:13:35.559 16944 ERROR nova.compute.manager     context)
2019-05-24 15:13:35.559 16944 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 5035, in _get_guest_config
2019-05-24 15:13:35.559 16944 ERROR nova.compute.manager     flavor, virt_type, self._host)
2019-05-24 15:13:35.559 16944 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/vif.py", line 558, in get_config
2019-05-24 15:13:35.559 16944 ERROR nova.compute.manager     vnic_type)
2019-05-24 15:13:35.559 16944 ERROR nova.compute.manager    File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/vif.py", line 521, in _get_config_os_vif
2019-05-24 15:13:35.559 16944 ERROR nova.compute.manager     inst_type, virt_type, vnic_type)
2019-05-24 15:13:35.559 16944 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/vif.py", line 134, in get_base_config
2019-05-24 15:13:35.559 16944 ERROR nova.compute.manager     virt=virt_type)
2019-05-24 15:13:35.559 16944 ERROR nova.compute.manager UnsupportedHardware: Requested hardware 'virtio1.0-net' is not supported by the 'kvm' virt driver 

After doing some research on google, I understand that this happens when the network interface model is defined as virtio1.0-net in the xml that’s fed to libvirt and libvirt does not consider that a valid name for a network interface model.
That said, why is Nova passing that model name to libvirt? I understand that it comes from libosinfo, but how is Nova getting that (wrong) information? If I look on other compute nodes, the model for the network interface is simply virtio.

Best regards,

Jean-Philippe Méthot
Openstack system administrator
Administrateur système Openstack
PlanetHoster inc.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190524/281446d2/attachment.html>