Description of problem: After a compute crash, VMs are restarted but nic order is wrong or new macs are injected: 1. Compute crashes, kills all the VMs running in it. 2. Once the Compute is brought online, the VMs are in STOPPED state (expected). 3. An operator starts again instance (UUID) fd87cb54-3726-40bb-9385-7fc2dcc50e38. Then, we see the following: ~~~~ on creation: id=net0,mac=00:00:00:f6:27:c6 id=net1,mac=00:00:00:f9:b1:87 id=net2,mac=00:00:00:12:37:82 <<<< gone id=net3,mac=00:00:00:00:00:01 after the compute reboot: id=net0,mac=00:00:00:f6:27:c6 id=net1,mac=00:00:00:f9:b1:87 id=net2,mac=00:00:00:00:00:01 id=net3,mac=00:00:00:fb:d3:94 <<<<< new ~~~~ Q: Why has that happened? A: It was triggered by an operator some while ago (no admin rights needed, it's enough to be the owner of the VM). The changes never got propagated until the instance's (forced) reboot. Version-Release number of selected component (if applicable): openstack-neutron-9.3.1-2.el7ost.noarch Thu Jun 15 18:52:29 2017 openstack-neutron-bigswitch-agent-9.42.1-3.el7ost.noarch Thu Jun 15 18:21:54 2017 openstack-neutron-bigswitch-lldp-9.42.1-3.el7ost.noarch Thu Jun 15 18:21:55 2017 openstack-neutron-common-9.3.1-2.el7ost.noarch Thu Jun 15 18:21:49 2017 openstack-neutron-lbaas-9.2.0-2.el7ost.noarch Thu Jun 15 18:52:29 2017 openstack-neutron-metering-agent-9.3.1-2.el7ost.noarch Thu Jun 15 18:53:46 2017 openstack-neutron-ml2-9.3.1-2.el7ost.noarch Thu Jun 15 18:46:42 2017 openstack-neutron-openvswitch-9.3.1-2.el7ost.noarch Thu Jun 15 18:53:43 2017 openstack-neutron-sriov-nic-agent-9.3.1-2.el7ost.noarch Thu Jun 15 18:57:13 2017 puppet-neutron-9.5.0-2.el7ost.noarch Thu Jun 15 18:59:06 2017 python-neutron-9.3.1-2.el7ost.noarch Thu Jun 15 18:21:48 2017 python-neutron-lbaas-9.2.0-2.el7ost.noarch Thu Jun 15 18:30:52 2017 python-neutron-lib-0.4.0-1.el7ost.noarch Thu Jun 15 18:21:45 2017 python-neutron-tests-9.3.1-2.el7ost.noarch Thu Jun 15 18:21:51 2017 python-neutronclient-6.0.0-2.el7ost.noarch Thu Jun 15 18:20:32 2017 openstack-nova-api-14.0.6-2.el7ost.noarch Thu Jun 15 18:52:33 2017 openstack-nova-cert-14.0.6-2.el7ost.noarch Thu Jun 15 18:52:33 2017 openstack-nova-common-14.0.6-2.el7ost.noarch Thu Jun 15 18:49:11 2017 openstack-nova-compute-14.0.6-2.el7ost.noarch Thu Jun 15 18:52:26 2017 openstack-nova-conductor-14.0.6-2.el7ost.noarch Thu Jun 15 18:52:32 2017 openstack-nova-console-14.0.6-2.el7ost.noarch Thu Jun 15 18:52:32 2017 openstack-nova-migration-14.0.6-2.el7ost.noarch Thu Jun 15 18:52:30 2017 openstack-nova-novncproxy-14.0.6-2.el7ost.noarch Thu Jun 15 18:52:33 2017 openstack-nova-scheduler-14.0.6-2.el7ost.noarch Thu Jun 15 18:52:32 2017 puppet-nova-9.5.0-6.el7ost.noarch Thu Jun 15 18:59:03 2017 python-nova-14.0.6-2.el7ost.noarch Thu Jun 15 18:49:10 2017 python-novaclient-6.0.0-3.el7ost.noarch Thu Jun 15 18:20:53 2017 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
*** This bug has been marked as a duplicate of bug 1691715 ***