ESTABLISH LOCAL CONNECTION FOR USER: runner

[callm...@gmail.com]

When running jobs from AWX, I noticed that the execution environment did not have the community.general collection.

I made an execution environment, adding community.general and several others, imported it to a container registry, and added it to AWX.

I configured a job template to use my new execution environment, but when I run the job it fails.

Looking at the output, I notice it is trying to connect as runner, instead of using the machine credentials.

I figure this is due to the environment running as a container; however, we have an old version of AWX running in docker that doesn't have that issue, so I'm trying to figure out why it is trying to authenticate as runner, instead of using my machine creds.

I'm figuring there's gotta be something I've missed in the build of my EE.

Thanks,

Shawn

[callm...@gmail.com]

as an example, when the playbook runs, gathering facts I see:

TASK [Gathering Facts] *********************************************************09:37:44

28

task path: /runner/project/troubleshoot.yaml:2

29

<lnx33425.csxt.csx.com> ESTABLISH LOCAL CONNECTION FOR USER: runner

[callm...@gmail.com]

nevermind, I'm an idiot :). I had forced a local connection on the inventory while testing, and forgot to take it out.