Description of problem: With "ovs+dpdk" setup, while trying to spawn VLAN aware VM hitting the issue. following error message reported in "nova show <instance>" output. ~~~ | fault | {"message": "Exceeded maximum number of retries. Exceeded max scheduling attempts 3 for instanc e 9c11637a-8d18-401c-a9c4-018765110d90. Last exception: OVS configuration failed with: Unexpected error while running command. | | | Command: sudo nova-rootwrap /etc/nova/rootwrap", "code": 500, "details": " File \"/usr/lib/pyt hon2.7/site-packages/nova/conductor/manager.py\", line 492, in build_instances | | | filter_properties, instances[0].uuid) | | | File \"/usr/lib/python2.7/site-packages/nova/scheduler/utils.py\", line 184, in populate_retr y | | | raise exception.MaxRetriesExceeded(reason=msg) | ~~~ Version-Release number of selected component (if applicable): RHEL OSP 10 How reproducible: Everytime for Cu. Steps to Reproduce: 1. Create sub port. 2. Try to spawn using the port. 3. Instance is going into ERROR state. Actual results: Instance spawn operation is getting failed. Expected results: It should get successfully completed. Additional info:
Jakub, can you please triage?
(In reply to Assaf Muller from comment #5) > Jakub, can you please triage? Will have a look
The issue is that Nova doesn't support vhostuser for conversion to os-vif type in Newton - this patch https://review.openstack.org/#/c/334048/
To describe the issue better is that Nova started using os-vif library. As this transition is in progress, support for trunk was implemented only to os-vif omitting nova code. 2017-01-05 01:50:43.697 40178 DEBUG nova.network.os_vif_util [req-b57615e3-07d3-4aa4-bc7d-d0dba791e70d 30cf353c5c094ad1b6060d55f7d7feff 47e925e032b14635ac2e656811b5c28b - - -] No conversion for VIF type vhostuser yet nova_to_osvif_vif /usr/lib/python2.7/site-packages/nova/network/os_vif_util.py:378 Nova in Newton doesn't support transition from libvirt vif to os-vif for vhostuser vif type but only for ovs vif type. os-vif takes care of creating provided tbr-<> bridge. That explains the error about missing trunk bridge. Once os-vif creates trunk bridge, ovsdb handler in Neutron will be triggered based on ovsdb events. I'll try to provide scratch build for nova containing the patch from comment 7 to test, whether we can move forward with trunk+dpdk
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0319.html