Steps to reproduce
1. Create env
2. Add network called san
fuel2 network-group create -N 1 -C 172.17.32.64/27 -V 1362 -g 172.17.32.65 san
3. Upload network-template (see attachment)
4. Add controllers/computes
5. Hit deploy changes
6. Emulate deployment fail (e.g. kill puppet on any node)
7. Hit deploy changes one more time to restart deployment
Expected behaviour:
Deployed environment
Actual behaviour:
Error: "Some untagged networks are assigned to the same physical interface. You should assign them to different physical interfaces."
Diagnostic Snapshot: https://drive.google.com/open?id=0B0kV2KAlVj3NQTM4Yk82bkZKejg
Description of the environment:
[root@fuel ~]# shotgun2 short-report
cat /etc/fuel_build_id:
495
cat /etc/fuel_build_number:
495
cat /etc/fuel_release:
9.0
cat /etc/fuel_openstack_version:
mitaka-9.0
rpm -qa | egrep 'fuel|astute|network-checker|nailgun|packetary|shotgun':
fuel-release-9.0.0-1.mos6349.noarch
fuel-misc-9.0.0-1.mos8460.noarch
python-packetary-9.0.0-1.mos140.noarch
fuel-bootstrap-cli-9.0.0-1.mos285.noarch
fuel-migrate-9.0.0-1.mos8460.noarch
shotgun-9.0.0-1.mos90.noarch
fuel-notify-9.0.0-1.mos8460.noarch
nailgun-mcagents-9.0.0-1.mos750.noarch
python-fuelclient-9.0.0-1.mos325.noarch
fuel-9.0.0-1.mos6349.noarch
fuel-utils-9.0.0-1.mos8460.noarch
fuel-setup-9.0.0-1.mos6349.noarch
fuel-provisioning-scripts-9.0.0-1.mos8743.noarch
fuel-library9.0-9.0.0-1.mos8460.noarch
network-checker-9.0.0-1.mos74.x86_64
fuel-agent-9.0.0-1.mos285.noarch
fuel-ui-9.0.0-1.mos2717.noarch
fuel-ostf-9.0.0-1.mos936.noarch
fuelmenu-9.0.0-1.mos274.noarch
fuel-nailgun-9.0.0-1.mos8743.noarch
rubygem-astute-9.0.0-1.mos750.noarch
fuel-mirror-9.0.0-1.mos140.noarch
fuel-openstack-metadata-9.0.0-1.mos8743.no
I think this bug is related https:/
In both cases we use re-deploy mechanism