Deployment failed with Failed tasks: Task[swift-proxy_storage/12] Stopping the deployment process!

[Volodymyr Shypyguzov]

Deployment with 3 controllers, NeutronVLAN with reset and re-deploy test failed

Steps to reproduce:
1. Create new environment
2. Choose Neutron, VLAN
3. Add 5 controller
4. Add 2 compute
5. Add 1 cinder
6. Change default disks partitioning for cinder node for 'vdb'
7. Verify networks
8. Deploy the environment <<< FAIL

Expected result: Deployment completed successfully
Actual result: Deployment failed with
2016-06-21 12:33:37 ERR (/Stage[main]/Swift::Dispersion/Exec[swift-dispersion-populate]/returns) change from notrun to 0 failed: swift-dispersion-populate returned 1 instead of one of [0]

Diagnostic snapshot: https://drive.google.com/a/mirantis.com/file/d/0B7rLGkmwHi0OaGJUTFNSRHVfQkk/view?usp=sharing

cat /etc/fuel_build_id:
 490
cat /etc/fuel_build_number:
 490
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
 rubygem-astute-9.0.0-1.mos750.noarch
 fuel-mirror-9.0.0-1.mos140.noarch
 shotgun-9.0.0-1.mos90.noarch
 fuel-openstack-metadata-9.0.0-1.mos8743.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

(Probably 'tun_5_ctrl_ceph_ephemeral' testgroup)

[Kyrylo Galanov (kgalanov)]

I need access to the environment to be able to debug.

It is a network issue:
ERROR with remote server 10.109.10.3:6001/2: Connection refused
ERROR with remote server 10.109.10.9:6001/1: Connection refused
ERROR with remote server 10.109.10.4:6001/2: Connection refused

rsync: failed to connect to 10.109.10.9 (10.109.10.9): Connection refused (111)
rsync: failed to connect to 10.109.10.3 (10.109.10.3): Connection refused (111)
rsync: failed to connect to 10.109.10.8 (10.109.10.8): Connection refused (111)

[Kyrylo Galanov (kgalanov)]

The bug could not be reproduced. No updates from bug reporter.