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

last playbook with debian stretch #23

Open
Regimbal opened this issue Oct 4, 2019 · 0 comments
Open

last playbook with debian stretch #23

Regimbal opened this issue Oct 4, 2019 · 0 comments

Comments

@Regimbal
Copy link

Regimbal commented Oct 4, 2019

Here is my situation:

  • I run Ansible and Vagrant on a Mac OSX
  • if I run the playbook with Vagrant deploying a debian Buster, everything runs fine.
  • When using a debian stretch, vagrant stops at parsing the playbook, finding an error in the letsencrypt main task.

From what I've observed, this coud come from the Ansible version installed on the Vagrant guest machine.
I tried checking out the repo to a commit where Debian Stretch was the main distribution (in such release vagrant file installs Ansible with pip)
There, Vagrant stops claiming that pip is not installed.

Is there any way to correct this please?

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

1 participant