Machine credential not working

[jschilen]

Hello,

I’m using AWX on minikube. I’m working on a project to automate the AWX config using infra. I’ve got it working to create an RHV credential, Project, and job template.

Whenever I try to get it to create a machine credential type with the example here: controller_configuration/roles/credentials at devel · redhat-cop/controller_configuration · GitHub

It causes the credentials task to fail.

The file in controller_credentials.d looks like this:

controller_credentials:
  - name: KSU-CREDENTIAL-MACHINE / localuser
    description: awx-build Testing Machine Credential example with become_method input
    credential_type: Machine
    inputs:
      username: localuser
      password: password
      become_method: sudo

TASK [infra.controller_configuration.credentials : Managing Controller Credentials | Wait for finish the credential management] ***15:27:59

165

**FAILED - RETRYING: [localhost]: Managing Controller Credentials | Wait for finish the credential management (30 retries left).**

166

changed: [localhost] => (item=None)

167

failed: [localhost] (item=None) => {"attempts": 1, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}

168

fatal: [localhost]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}

I have another credential file in the same directory of type Red Hat Virtualization that works fine. It just seems to be as soon as I try to create a Machine type.

Am I doing something wrong?
Can I get more detailed errors somehow?

[jschilen]

Well here I am 3 days later and the same code just worked. There’s no difference in the code so I don’t know what I changed elsewhere that made this work ¯_(ツ)_/¯.

[jbericat (Jordi Bericat Ruz)]

Hello @jschilen welcome to the Ansible Forum Community!

Good to see you came up with a solution yourself with no effort at all

Just for housekeeping sake, may I ask you to tick the solved check ? (of course, you can set your own response as the solution!)

In any case, if the issue pops up again, don’t hesitate to reach out. We’re here and more than happy to help!

Cheers