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

[chuanchang]

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

[Dannyb48]

@chuanchang you need to set the following in your linchpin.conf

[evars]
auth_debug = True

To see the ouput of the authentication error. There are a couple possible issues:

• It's quite possible that the $CREDS_PATH is not to the appropriate path to where the clouds.yaml can be found
  or
• in my experience, if the clouds.yaml file is not vault encrypted. Then you also need to set the following evars in the linchpin.conf:

vault_encryption = False 
vaul_pass = '''

[chuanchang]

[evars]
auth_debug = True

I still got the same issue w/ the following configuration in the linchpin.conf

$ grep -B4 debug workspace/linchpin/linchpin.conf
[evars]

# enables the ansible --check option
# _check_mode = False
debug_mode = True
auth_debug = True

To see the ouput of the authentication error. There are a couple possible issues:

* It's quite possible that the `$CREDS_PATH` is not to the appropriate path to where the clouds.yaml can be found
  or

* in my experience, if the `clouds.yaml` file is not vault encrypted. Then you also need to set the following evars in the linchpin.conf:

vault_encryption = False 
vaul_pass = '''

I think it's not a root reason, because I can successfully provision a VM in non-container environment, but I need to run linchpin command inside work directory, otherwise, I can hit the same issue.

[Dannyb48]

Right, Which makes me think its something with the linchpin in the container locating the linchpin.conf properly. Which I'm hoping some of the advice Alex provided in #1741 can help here.

[abraverm]

@chuanchang , can we close this ticket?