Failed to connect to upstream repo(s)

[Jeffrey Olsen]

I'm receiving the following Task Error when running "setup-everything.yml"

PLAY [Cloning the upstream repo mirror] ***************************************

TASK: [Sync the upstream repo(s)] *********************************************
failed: [aio1_repo_container-18d5780d] => {"changed": true, "cmd": "rsync -avzlHAX --exclude=/repos --exclude=/mirror --exclude=/rpcgit --exclude=/openstackgit --exclude=/python_packages rpc-repo.rackspace.com::openstack_mirror /var/www/repo", "delta": "0:02:22.294006", "end": "2015-07-04 14:15:19.981820", "rc": 10, "start": "2015-07-04 14:12:57.687814", "warnings": ["Consider using synchronize module rather than running rsync"]}
stderr: rsync: failed to connect to rpc-repo.rackspace.com (23.253.147.41): Connection timed out (110)
rsync error: error in socket IO (code 10) at clientserver.c(128) [Receiver=3.1.0]

FATAL: all hosts have already failed -- aborting

PLAY RECAP ********************************************************************
           to retry, use: --limit @/root/setup-everything.retry

[Kevin Carter (kevin-carter)]

Hi Jeffery, I've attempted to recreate / troubleshoot this issue and I'm not able recreate the problem and I've been testing in a few different locations.

The generated command `rsync -avzlHAX --exclude=/repos --exclude=/mirror --exclude=/rpcgit --exclude=/openstackgit --exclude=/python_packages rpc-repo.rackspace.com::openstack_mirror /var/www/repo` is running without issue in the two test environments that I spun up.

I'm curious if you're able to run that command from within the repo container in your environment? You should be able to get access to the repo container from the aio1 host machine using the following commands:
# ssh aio1_repo_container-18d5780d
# su - nginx
# rsync -avzlHAX --exclude=/repos --exclude=/mirror --exclude=/rpcgit --exclude=/openstackgit --exclude=/python_packages rpc-repo.rackspace.com::openstack_mirror /var/www/repo

Also are you behind some kind of a proxy?

Anything else you may be able to share with us will be greatly appreciated and hopefully we can track this issue down for you and or get you pointed in the right direction.

[Jeffrey Olsen (jeffrey-olsen)]

Thanks Kevin - You are correct. I was able to successfully deploy outside of the normal LAN that I use and wasn't able to recreate the error. It seems to have been an issue with the proxy in my orgs environment which has been resolved and I'm now able to connect to the repo from there as well. Thanks for your help.

[Launchpad Janitor (janitor)]

[Expired for openstack-ansible because there has been no activity for 60 days.]