-
Notifications
You must be signed in to change notification settings - Fork 22
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
Error: privilege output closed while waiting for password prompt #18
Comments
Hi @DebtFromAbove - thanks for reporting this issue. Have you tried to specify a specific number, e.g. |
I've just tried that, specifying 5.2.22 and it appears to work, at least it gets past the task that had the issue before, but unfortunately it didn't succeed. It appears that it failed to upgrade (remove and install new) from 5.2.18 to 5.2.22. Here is the latest output:
|
I've got an idea why the first attempt failed. Looking at your code, it specified If that is the case I am running ansible on windows using Cygwin64. This isn't supported by ansible currently but seems to work for everything i've needed so far (including integration with vagrant). But it seems VBoxManage is not a command that is accessible in the current cygwin path on windows, even though I'm sure those command line virtualbox commands are accessible somewhere in windows. It might just be a case of needing to modify the cygwin path to add in their location Doesn't explain why it didn't upgrade to 5.2.22 when i specified the version directly though |
Hi, I get the error written in the issue title when the role tries to auto detect the Virtualbox guest additions version.
I'm running ansible 2.6.1 with python 2.7.13. The guest VM is ubuntu 18.04 LTS running xubuntu desktop, the command I am running is as follows:
ansible-playbook -i ./hosts --limit=netboot_test --vault-password-file=./vault_pass.txt -u simon -K -v main.yml
and the playbook I am running looks like:
The -K option above causes ansible playbook command to prompt me for the sudo password and I haven't had a problem like this with any of my other roles or playbooks.
I get the same result when using
become_method: sudo
The output that I get is as follows:
Any help or suggestions appreciated.
The text was updated successfully, but these errors were encountered: