-
-
Notifications
You must be signed in to change notification settings - Fork 646
Malformed Ansible Version #2166
Comments
I've tried using Ansible installed via |
It looks like the error is showing you have an issue with the Vagrantfile?
The first line there? |
@geerlingguy - I'm using a Composer managed version of DrupalVM, so my Vagrantfile simply references that and custom config. Vagrantfile:
Custom config
|
@geerlingguy I think Ansible has changed the way it outputs it's version string in the newest versions, and Vagrant does not properly parse it. A colleague had this error today, and used
|
I'm getting the same error as well. Didn't know if it was from Ansible or the Apple updates from Monday (May 24). I did update Ansible yesterday too, via Homebrew. |
I have just had a look around, and I can't seem to find an existing bug report for this anywhere on an upstream project. I would expect more users will be affected as they upgrade/install ansible, I'd assume that this would affect Linux users too. |
Ah... then yes, this is a bug in the version comparison: drupal-vm/lib/drupalvm/vagrant.rb Lines 60 to 68 in fb4675d
Also note that |
A quick fix is to override the minimum ansible version (https://github.com/geerlingguy/drupal-vm/blob/master/default.config.yml#L53):
See if that works? |
Could you try out #2167? It should work for all version strings unless a random number was introduced before the version number. ansible 2.1.3 # works
ansible 2.1.3-beta # works
ansible [core 2.13] # works
ansible 3 [core 3.13] # would not work https://github.com/rubygems/rubygems/blob/v3.2.18/lib/rubygems/version.rb#L157 |
Ran into this issue today after updating to vagrant 2.2.16, with Cheers |
Issue #2166: Fix new ansible version output doesnt match regex
Seems like that PR fixed it, thanks to @oxyc! I'll get this into the 6.0.4 release to be delivered...soonish. |
Issue Type
Your Environment
Your OS
Full console output
Summary
I cannot seem to run
vagrant up
with newest version of Ansible. It appears as if the version number is displayed in brackets now?The text was updated successfully, but these errors were encountered: