Traceback on spawning instance with vif model e1000

[Wendy Mitchell]

Title
-----------------
Traceback on spawning instance with vif model e1000

Brief Description
-----------------
STX: Traceback in nova compute on spawning instance with vif model e1000

Severity
--------
Major

Steps to Reproduce
------------------

Create an image with vif model metadata e1000
Boot a volume from the image
tenant2 attempts to launch the instance (remote storage)

name | tenant2-vif_img_e1000-16
created | 2018-09-04T06:22:19Z

Expected Behavior
------------------
Correct instance spawn failure/scheduling issue

Actual Behavior
----------------
The instance schedules on compute-1 (at 2018-09-04 06:22:28.964) but libvirt error is reported as follows

uuid=3b23c4ed-fedc-4e82-9fbe-229841c963f3, name=instance-0000011f, display_name=tenant2-vif_img_e1000-16, scheduled=1

2018-09-04 06:22:43.096 56068 ERROR nova.virt.libvirt.guest [req-adf40d85-994d-4beb-b594-b1062466f801 1cc86c5d7a084ab3bec457e9bf10a0dd 2ede711743b64e3bb7a24c4b4b34fcac - default default] Error defining a guest with XML: <domain type="kvm">
...
: libvirtError: internal error: Wrong or no <model> 'type' attribute specified with <interface type='vhostuser'/>. vhostuser requires the virtio-net* frontend

2018-09-04 06:22:43.098 56068 ERROR nova.virt.libvirt.driver [req-adf40d85-994d-4beb-b594-b1062466f801 1cc86c5d7a084ab3bec457e9bf10a0dd 2ede711743b64e3bb7a24c4b4b34fcac - default default] [instance: 3b23c4ed-fedc-4e82-9fbe-229841c963f3] Failed to start libvirt guest

ERROR (ResourceInErrorState): `Server` resource is in the error state due to 'Exceeded maximum number of retries. Exceeded max scheduling attempts 3 for instance 3b23c4ed-fedc-4e82-9fbe-229841c963f3. Last exception: internal error: Wrong or no <model> 'type' attribute specified with <interface type='vhostuser'/>. vhostuser requires'.

Reproducibility
---------------
Reproducible

System Configuration
--------------------
Standard storage lab

Branch/Pull Time/Commit
-----------------------
master as of 2018-09-01_20-18-00

Timestamp/Logs
--------------
see above

[Ghada Khalil (gkhalil)]

As per Matt Peters, this is a known issue of not being able to support emulated devices with OVS-DPDK. It is not specific to StarlingX.

[Ghada Khalil (gkhalil)]

Marking as stx.2019.03 for now. Need to investigate whether we can address this through configuration or whether we want to report a bug to ovs-dpdk

[Ghada Khalil (gkhalil)]

This is a limitation of ovs-dpdk. It is not specific to StarlingX. Marking as Won't Fix.