The scenario proposed in upstream https://bugs.launchpad.net/nova/+bug/1501735 description has been used for verification (the time.sleep(2) has been added to nova code and the script allowing to create an instance with multiple network interfaces has been run 20 times). All test iterations were OK: instances with multiple network interfaces were created and launched successfully and there were no duplicate interfaces in the instance info cache.
It has been verified on (3 controllers+2 computes, vlan, cinder lvm): build_number: openstack_ version: network- checker| nailgun| packetary| shotgun' : 9.0.0-1. mos8259. noarch fuelclient- 9.0.0-1. mos301. noarch 0.0-1.mos6325. noarch ing-scripts- 9.0.0-1. mos8611. noarch 9.0.0-1. mos263. noarch 9.0.0-1. mos2641. noarch 9.0.0-1. mos8259. noarch 9.0.0-1. mos921. noarch 9.0.0-1. mos87.noarch packetary- 9.0.0-1. mos130. noarch -cli-9. 0.0-1.mos272. noarch 9.0.0-1. mos8611. noarch 9.0.0-1. mos6325. noarch astute- 9.0.0-1. mos733. noarch 9.0.0-1. mos130. noarch -metadata- 9.0.0-1. mos8611. noarch 9.0.0-1. mos8259. noarch 9.0.0-1. mos6325. noarch mcagents- 9.0.0-1. mos733. noarch checker- 9.0.0-1. mos72.x86_ 64 9.0.0-1. mos8259. noarch 0-9.0.0- 1.mos8259. noarch 9.0.0-1. mos272. noarch
[root@nailgun ~]# shotgun2 short-report
cat /etc/fuel_build_id:
154
cat /etc/fuel_
154
cat /etc/fuel_release:
9.0
cat /etc/fuel_
mitaka-9.0
rpm -qa | egrep 'fuel|astute|
fuel-misc-
python-
fuel-9.
fuel-provision
fuelmenu-
fuel-ui-
fuel-migrate-
fuel-ostf-
shotgun-
python-
fuel-bootstrap
fuel-nailgun-
fuel-setup-
rubygem-
fuel-mirror-
fuel-openstack
fuel-notify-
fuel-release-
nailgun-
network-
fuel-utils-
fuel-library9.
fuel-agent-
[root@nailgun ~]#
The scenario proposed in upstream https:/ /bugs.launchpad .net/nova/ +bug/1501735 description has been used for verification (the time.sleep(2) has been added to nova code and the script allowing to create an instance with multiple network interfaces has been run 20 times). All test iterations were OK: instances with multiple network interfaces were created and launched successfully and there were no duplicate interfaces in the instance info cache.