Public bug reported: Nova boot fails when freed SRIOV port is used for booting
steps to reproduce: ================== 1.create a SRIOV port 2.boot a vm -->Boot is successful and vm gets ip 3.now delete the vm using nova delete --successful (mac is released from VF) 4.using the port created in step 1 boot a new vm. VM fails to boot with following error [01;31m2016-04-20 10:55:05.005 TRACE nova.compute.manager ^[[01;35m[instance: a47344fb-3254-4409-9c23-55e3cde693d9] ^[[00m hostname=instance.hostname) ^[[01;31m2016-04-20 10:55:05.005 TRACE nova.compute.manager ^[[01;35m[instance: a47344fb-3254-4409-9c23-55e3cde693d9] ^[[00mPortNotUsableDNS: Port 7219a612-014e-452e-b79a-19c87cc33db4 not usable for instance a47344fb-3254-4409-9c23-55e3cde693d9. Value vm4 assigned to dns_name attribute does not match instance's hostname vmtest4 ^[[01;31m2016-04-20 10:55:05.005 TRACE nova.compute.manager ^[[01;35m[instance: a47344fb-3254-4409-9c23-55e3cde693d9] ^[[00m Expected : ========= As port is unbound in step 3 we should be able to bind it in step 4. The setup consists of controller and compute node with Mellanox card enabled for SRIOV. Ubuntu 14.04 qcow2 image is used for tenant VM boot Tested the above with MItaka code. ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1572509 Title: Nova boot fails when freed SRIOV port is used for booting Status in OpenStack Compute (nova): New Bug description: Nova boot fails when freed SRIOV port is used for booting steps to reproduce: ================== 1.create a SRIOV port 2.boot a vm -->Boot is successful and vm gets ip 3.now delete the vm using nova delete --successful (mac is released from VF) 4.using the port created in step 1 boot a new vm. VM fails to boot with following error [01;31m2016-04-20 10:55:05.005 TRACE nova.compute.manager ^[[01;35m[instance: a47344fb-3254-4409-9c23-55e3cde693d9] ^[[00m hostname=instance.hostname) ^[[01;31m2016-04-20 10:55:05.005 TRACE nova.compute.manager ^[[01;35m[instance: a47344fb-3254-4409-9c23-55e3cde693d9] ^[[00mPortNotUsableDNS: Port 7219a612-014e-452e-b79a-19c87cc33db4 not usable for instance a47344fb-3254-4409-9c23-55e3cde693d9. Value vm4 assigned to dns_name attribute does not match instance's hostname vmtest4 ^[[01;31m2016-04-20 10:55:05.005 TRACE nova.compute.manager ^[[01;35m[instance: a47344fb-3254-4409-9c23-55e3cde693d9] ^[[00m Expected : ========= As port is unbound in step 3 we should be able to bind it in step 4. The setup consists of controller and compute node with Mellanox card enabled for SRIOV. Ubuntu 14.04 qcow2 image is used for tenant VM boot Tested the above with MItaka code. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1572509/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp