Description of problem: After removing a VM with a PF allocated, the link state of the interface is down. This state avoids the VFs assigned to that PF to be properly allocated. Version-Release number of selected component (if applicable): How reproducible: In an SRIOV environment with VFs and PFs with OSP10 GA. Steps to Reproduce: neutron port-create nfv_sriov --binding:vnic-type direct-physical --name pf1 neutron port-create nfv_sriov --binding:vnic-type direct --name vf1 nova boot test-passthrough --security-groups allowall --flavor m1.small.numapin --key-name key --image centos_pwd2 --nic port-id=$(neutron port-list | grep pf1 | awk '{print $2}') nova delete test-passthrough nova boot test-sriov --security-groups allowall --flavor m1.small.numapin --key-name key --image centos_pwd2 --nic port-id=$(neutron port-list | grep vf1 | awk '{print $2}') ERROR related to: {"message": "internal error: Unable to configure VF 1 of PF 'p3p1' because the PF is not online. Please change host network config to put the PF online.", "code": 500, "details": " File \"/usr/lib/python2.7/site-packages/nova/compute/manager.py\", line 1779, in _do_build_and_run_instance | | | filter_properties) Additional info: Changing the NM_CONTROLLED flag to yes in the SRIOV NIC's config, it will set link state to UP and allow the allocation of the VFs.
Attached the stable/newton backport.
This was already fixed and available in OSP 10, closing as a dup. *** This bug has been marked as a duplicate of bug 1392585 ***
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days