Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't authenticate to ansible vault since 3.2.11 #362

Open
Lusitaniae opened this issue Apr 10, 2024 · 5 comments
Open

can't authenticate to ansible vault since 3.2.11 #362

Lusitaniae opened this issue Apr 10, 2024 · 5 comments

Comments

@Lusitaniae
Copy link

Lusitaniae commented Apr 10, 2024

Rundeck version: 4.17.6-20240402

I have Ansible Playbook Node Workflow with Vault Pass Storage Path: keys/production/ansible/.vault

That's a key stored in Rundeck defaults KV store

After going through all recent releases of this plugins seems like 3.2.11 and 4.0.0 both are unable to open the vault file

3.2.10 and earlier releases are all working 👍

[WARNING]: Error in vault password file loading (None): Invalid vault password
was provided from script (/tmp/ansible-runner419321991769154953ansible-script-
vault-client.py)
ERROR! Invalid vault password was provided from script (/tmp/ansible-runner419321991769154953ansible-script-vault-client.py)
Failed: AnsibleNonZero: ERROR: Ansible execution returned with non zero code.

Debug logs show the invokation looking like

encryptVariable ansible_become_password: [ansible-vault, encrypt_string, --vault-id, internal-encrypt@/tmp/ansible-runner3534718919055327790ansible-script-vault-client.py]
 procArgs: [ansible-playbook, site.yml, --vault-id, internal-encrypt@/tmp/ansible-runner3534718919055327790ansible-script-vault-client.py, -l, rundeck1, -vvv, --vault-id, /tmp/ansible-runner3534718919055327790ansible-script-vault-client.py, --private-key=/tmp/ansible-runner2368737503622131914id_rsa, --user=rundeck_user, --timeout=30, --become, --extra-vars=@/tmp/ansible-runner4868465325436002323become-extra-vars, -i, inventory, -l, node1, --tags, app]
@madsi1m
Copy link

madsi1m commented Jul 4, 2024

I also have this exact issue where 3.2.10 works but anything newer does not.

We use SSH login with passwords, starting rundeck manually outside of the service i noticed when i trigger an ansible job, the console is waiting for me to press enter at the ansible ssh password prompt. It looks like the password is entered and i need to press enter for it to continue.

SSH password: <manually press enter>
ECOME password[defaults to SSH password]: <manually press enter>

If i don't press enter i get the same error as @Lusitaniae.

@d4e-sluksch
Copy link

@Lusitaniae according to #380, does your vault password file contains multiple lines?

@jimr6007
Copy link

it's not that, it's something more low level, even things like using a job option to allow a user to enter a password is broken since 3.2.11, from what I can tell, lot's of things that involve some user input are affected by this issue

@madsi1m
Copy link

madsi1m commented Aug 19, 2024

I can confirm in my testing that this has still not been resolved (tested 4.0.4).

@lennardk
Copy link

I seem to have also ran into this. In my case, similar to madsi1m, I've seen it when using both a vault and ssh password authentication.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants