It works on the repo itself: *root@maas:/opt/openstack-ansible/playbooks# ansible repo_all -m shell -a "curl http://localhost:8181/os-releases/ <http://localhost:8181/os-releases/>"* Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e @/etc/openstack_deploy/user_variables.yml " node01_repo_container-82b4e1f6 | SUCCESS | rc=0 >> <html> <head><title>Index of /os-releases/</title></head> <body bgcolor="white"> <h1>Index of /os-releases/</h1><hr><pre><a href="../">../</a> <a href="14.0.1/">14.0.1/</a> 16-Nov-2016 14:47 - </pre><hr></body> </html> % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 287 0 287 0 0 59878 0 --:--:-- --:--:-- --:--:-- 71750
On 17 November 2016 at 15:22, Jesse Pretorius < jesse.pretor...@rackspace.co.uk> wrote: > > > > > *From: *Achi Hamza <h16m...@gmail.com> > *Date: *Thursday, November 17, 2016 at 1:57 PM > *To: *Jesse Pretorius <jesse.pretor...@rackspace.co.uk>, " > OpenStack-operators@lists.openstack.org" <OpenStack-operators@lists. > openstack.org> > *Subject: *Re: [Openstack-operators] [openstack-dev] [openstack-ansible] > pip issues > > > > Thank you Jesse, but these iptables rules are just applied on the > deployment node not the host nodes. do i have to omit these rules even on > the deployment node ? > > > > Thank you > > > > Ah, then that’s a red herring. As long as your hosts can reach the > internet through it, then you’re good on that front. > > > > Let’s go back to verifying access to the repo – try checking access from > the repo server to itself: > > > > ansible repo_all -m uri -a "url=http://localhost:8181/os-releases/" > > > > or > > > > ansible repo_all –m shell –a "curl http://localhost:8181/os-releases/" > > > > ------------------------------ > Rackspace Limited is a company registered in England & Wales (company > registered number 03897010) whose registered office is at 5 Millington > Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy > can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail > message may contain confidential or privileged information intended for the > recipient. Any dissemination, distribution or copying of the enclosed > material is prohibited. If you receive this transmission in error, please > notify us immediately by e-mail at ab...@rackspace.com and delete the > original message. Your cooperation is appreciated. > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > >
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators