Instance cannot create with network driver e1000 and rtl8139

[krishna pavan]

Brief Description
Instance cannot able to create with particular network driver, Instance status show Error.

This issue is observed when network drivers created with e1000 and rtl8139
Severity
--------
<Minor: System/Feature is not usable>

Steps to Reproduce
------------------
1. Create flavor and image
2. openstack image set --property hw_vif_model=e1000 VM-image1
3. Create Network and subnet
4. Create instance
7. Status of instance is showing as Error state.

Expected Behavior
------------------
Instance should be created without error

Actual Behavior
----------------
Instance is created and status was in error state
{u'message': u'Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures for instance 52ad22e8-901a-4f27-9448-057a809c116f.', u'code': 500, u'details': u' File "/var/lib/openstack/lib/python2.7/site-packages/nova/conductor/manager.py", line 610, in build_instances\n raise exception.MaxRetriesExceeded(reason=msg)\n', u'created': u'2019-07-03T11:17:44Z'}

Reproducibility
---------------
<Reproducible>
State if the issue is 100% reproducible.

System Configuration
--------------------
<Dedicated storage>

Branch/Pull Time/Commit
-----------------------
bootimage.iso 2019-06-28 01:30:00
ISO link:http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190628T013000Z/outputs/iso/
HelmChart Link:http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190628T013000Z/outputs/helm-charts/stx-openstack-1.0-17-centos-stable-latest.tgz

Last Pass
---------
No information about the last pass

Timestamp/Logs
--------------
Attached collect logs.

[Ghada Khalil (gkhalil)]

@Krishna, what vswitch_type are you using?
There is a known issue of not being able to support emulated devices with ovs-dpdk.
See https://bugs.launchpad.net/starlingx/+bug/1791685

[Ghada Khalil (gkhalil)]

The collect_network_driver.log is not actually a collect tarball. It just appears to be a list of filenames that are typically included in the collect tarball. This has no useful information. No further investigation can be done on this bug until the vswitch_type is specified and the proper logs are provided.

[Ghada Khalil (gkhalil)]

@Krishna, please provide the requested information. Thanks.
(1) confirm the vswitch type configured
(2) provide the proper logs

[krishna pavan (ksamudrx)]

1. vswitch(controller-0) is configured with ovs-dpdk.
2. Attached dmesg,nova container logs.

[Ghada Khalil (gkhalil)]

Thanks for the information. Given that ovs-dpdk is used, this is expected behavior as ovs-dpdk does not support emulated devices. See https://bugs.launchpad.net/starlingx/+bug/1791685

Please update the test-case to use containerized ovs (vswitch_type = none)