search

geerlingguy / tower-operator

DEPRECATED: This project was moved and renamed to: https://github.com/ansible/awx-operator
82 stars 34 forks source link

Error creating Tower CR #44

Closed tylerauerbeck closed 4 years ago

tylerauerbeck commented 4 years ago

When trying to create a Tower CR with the latest release, I see the following error in the operator logs:

u001b[0;34m1 plays in /opt/ansible/main.yml\u001b[0m\r\n\u001b[0;34m\u001b[\n\r\nPLAY [localhost] ***************************************************************\n\u001b[0;34mMETA: ran handlers\u001b[0m\r\n\u001b[0;34m\u001b[\n\r\nTASK [tower : Ensure configured Tower resources exist in the cluster.] *********\r\n\u001b[1;30mtask path: /opt/ansible/roles/tower/tasks/main.yml:2\u001b[0m\r\n\u001b[1;30m\u001b[\n\u001b[0;31mfailed: [localhost] (item=tower_memcached.yaml.j2) => {\"ansible_loop_var\": \"item\", \"item\": \"tower_memcached.yaml.j2\", \"msg\": \"Authentication or permission failure. In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in \\\"/tmp\\\". Failed command was: ( umask 77 && mkdir -p \\\"` echo /.ansible/tmp/ansible-tmp-1590759069.5041451-4700137306081 `\\\" && echo ansible-tmp-1590759069.5041451-4700137306081=\\\"` echo /.ansible/tmp/ansible-tmp-1590759069.5041451-4700137306081 `\\\" ), exited with result 1\", \"unreachable\": true}
tylerauerbeck commented 4 years ago

I'm currently noticing this in OpenShift 4.3. Going to confirm similar behavior on Kubernetes as well just to ensure this is a standard error and not something OCP related.

geerlingguy commented 4 years ago

@tylerauerbeck - Yeah I think Tower 3.7 support may need some more work. See https://github.com/geerlingguy/tower-operator/pull/45. I made some assumptions based on how AWX deploys, and it seems like they may work in AWX (using the public images) but might not work with the images from Red Hat's registry for Tower.