Hi everyone, I’ve recently had version mismatch issues with the ansible_local provisioner vagrant box. Same as reported here . This is the error I get when running trellis up with a fresh install via trellis new test4.com : ... ==> default: Running provisioner: ansible_local... default: Install…

@swalkinshaw , indeed a fresh install of Python solved it. I’ll loosely summarize in case anyone else encounters the same issue: Install pyenv via homebrew (Follow the post-install setup). (Re)Install python via pyenv. I did a ‘global’ install. It may not be necessary to destroy the vagrant box, b…

Did you see my reply in the other thread? [image] Ansible version error on vagrant up trellis Any issue with Vagrant and the ansible version is likely because you don’t have Ansible installed on your host machine. When Trellis’ Vagrantfile does not find an Ansible install…

Hi @swalkinshaw and @ben , Thanks for your quick replies. I have been using trellis-cli for a while now and this issue just came out of nowhere (though I want to somehow blame my upgrade to Ventura). That helps clear things up a bit, but why can’t my Vagrant file find the ansible in the virtualenv? …

Thanks for those details. Though something is definitely off :thinking: Based on your ansible --version output, it’s definitely being run from the virtualenv as it should be. executable location = /Users/conduct/Sites/example.com/trellis/.trellis/virtualenv/bin/ansible And yet it’s using the ansi…

Thanks @swalkinshaw . The additions to the which method returned (as expected/hoped) MBP-2020:example.com conduct$ trellis up Starting galaxy role install process - ... Running command => vagrant up which ansible-playbook /Users/conduct/Sites/example.com/trellis/.trellis/virtualenv/bin/ansible-pla…

Even stranger… [image] conductdesign: Looks like the path is being output fine from within the which method, but not returned? Again, I don’t know ruby, so maybe my test is meaningless. Yeah that change won’t works since Ruby implicitly uses the last value as the return value, and by having …

Thanks for the suggestions. I added the debug puts as suggested and got this: (had to strip out a bunch of the uninteresting bits. Scroll to bottom for the output from local_provisioning) Running command => vagrant up --debug INFO global: Vagrant version: 2.3.4 INFO global: Ruby version: 2.7.6 …

I had looked into those system calls but didn’t get you to debug them for some reason, so great idea. That seems to be the problem :tada: Python should work fine regardless of x86; you just need to re-install it from scratch I think.

@conductdesign I moved all these replies to your other thread to keep it together. Your problem is likely different than some other people’s.

Weird how things line up. I’ve just spent the weekend cross-compiling Python for termux / aarch64… :partying_face: I’m not sure if you’ve ever run in Rosetta (perhaps opened a terminal in Rosetta, then tried to install Python / Trellis), but it’s possible pip has downloaded or built the x86_64 whee…

Ansible_local version mismatch

trellis

swalkinshaw April 22, 2023, 2:44pm 2

Did you see my reply in the other thread?