I just tried to run the latest ansible tower setup (2.1.0) and it failed installing redis with the following error:
TASK: [packages_el | install yum repositories] ******************************** ok: [localhost] => (item=http://download.opensuse.org/repositories/home:cedric-vincent/CentOS_CentOS-6/home:cedric-vincent.repo) => {"changed": false, "dest": "/etc/yum.repos.d/home:cedric-vincent.repo", "gid": 0, "group": "root", "item": "http://download.opensuse.org/repositories/home:cedric-vincent/CentOS_CentOS-6/home:cedric-vincent.repo";, "md5sum": "6bde4c4761979e3786e068ef764e27e7", "mode": "0644", "msg": "OK (306 bytes)", "owner": "root", "secontext": "unconfined_u:object_r:etc_t:s0", "sha256sum": "", "size": 306, "src": "/tmp/tmpLwijnm", "state": "file", "uid": 0, "url": "http://download.opensuse.org/repositories/home:cedric-vincent/CentOS_CentOS-6/home:cedric-vincent.repo"} failed: [localhost] => (item=https://copr.fedoraproject.org/coprs/jlaska/redis-28/repo/epel-6/jlaska-redis-28-epel-6.repo) => {"failed": true, "item": "https://copr.fedoraproject.org/coprs/jlaska/redis-28/repo/epel-6/jlaska-redis-28-epel-6.repo"} msg: Unsupported proxy scheme: https. Currently ansible only supports HTTP proxies. FATAL: all hosts have already failed -- aborting I had to edit roles/packages_el/vars/CentOS-6.yml and change the protocol for the URL for jlaska-redis-28-epel-6.repo to http from https to get it to work. Once I fixed the above, the script continued until hitting the following error: TASK: [postgres | determine if postgresql user exists] ************************ failed: [localhost] => {"changed": false, "cmd": ["psql", "postgres", "-tAc", "SELECT 1 FROM pg_roles WHERE rolname='awx'"], "delta": "0:00:00.038819", "end": "2015-01-08 15:09:26.522631", "failed": true, "failed_when_result": true, "rc": 2, "start": "2015-01-08 15:09:26.483812", "stdout_lines": []} stderr: psql: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/tmp/.s.PGSQL.5432"? ...ignoring TASK: [postgres | create the postgresql user for awx] ************************* failed: [localhost] => {"failed": true} msg: unable to connect to database: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/tmp/.s.PGSQL.5432"? FATAL: all hosts have already failed -- aborting To fix this I edited vi roles/postgres/tasks/conf.yml and added state=started to the postgres service definition ('configure postgresql to startup automatically'). I ran setup.sh again and it got past the previous error but then the following happened: TASK: [awx_install | create awx database schema] ****************************** failed: [localhost] => {"changed": false, "cmd": ["awx-manage", "syncdb", "--noinput"], "delta": "0:00:03.017540", "end": "2015-01-08 15:16:46.468519", "rc": 1, "start": "2015-01-08 15:16:43.450979", "stdout_lines": ["Syncing..."]} stderr: Traceback (most recent call last): File "/usr/bin/awx-manage", line 9, in <module> load_entry_point('ansible-tower==2.1.0', 'console_scripts', 'awx-manage')() File "/usr/lib/python2.6/site-packages/awx/__init__.py", line 91, in manage File "/usr/lib64/python2.6/site-packages/django/core/management/__init__.py", line 399, in execute_from_command_line utility.execute() File "/usr/lib64/python2.6/site-packages/django/core/management/__init__.py", line 392, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib64/python2.6/site-packages/django/core/management/base.py", line 242, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib64/python2.6/site-packages/django/core/management/base.py", line 285, in execute output = self.handle(*args, **options) File "/usr/lib64/python2.6/site-packages/django/core/management/base.py", line 415, in handle return self.handle_noargs(**options) File "/usr/lib/python2.6/site-packages/awx/lib/site-packages/south/management/commands/syncdb.py", line 92, in handle_noargs syncdb.Command().execute(**options) File "/usr/lib64/python2.6/site-packages/django/core/management/base.py", line 285, in execute output = self.handle(*args, **options) File "/usr/lib64/python2.6/site-packages/django/core/management/base.py", line 415, in handle return self.handle_noargs(**options) File "/usr/lib64/python2.6/site-packages/django/core/management/commands/syncdb.py", line 57, in handle_noargs cursor = connection.cursor() File "/usr/lib64/python2.6/site-packages/django/db/backends/__init__.py", line 162, in cursor cursor = util.CursorWrapper(self._cursor(), self) File "/usr/lib64/python2.6/site-packages/django/db/backends/__init__.py", line 132, in _cursor self.ensure_connection() File "/usr/lib64/python2.6/site-packages/django/db/backends/__init__.py", line 127, in ensure_connection self.connect() File "/usr/lib64/python2.6/site-packages/django/db/utils.py", line 99, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/usr/lib64/python2.6/site-packages/django/db/backends/__init__.py", line 127, in ensure_connection self.connect() File "/usr/lib64/python2.6/site-packages/django/db/backends/__init__.py", line 115, in connect self.connection = self.get_new_connection(conn_params) File "/usr/lib64/python2.6/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 115, in get_new_connection return Database.connect(**conn_params) django.db.utils.OperationalError: FATAL: password authentication failed for user "awx" stdout: Syncing... FATAL: all hosts have already failed -- aborting This is as far as I've got right now, I haven't got time to go further at this point but I thought I'd post my issues so far all the same. Guy -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/5d88340c-54af-4d2b-a45b-fd967e6135a9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
