Closed mark-jones-entanet closed 4 years ago
It looks like it is an ansible galaxy issue as if you use a direct link to the repo here it works.
seeing it to, worked last week.
Confirmed. This is definitely something with Galaxy API data: The latest version shown on https://galaxy.ansible.com/geerlingguy/php is 3.7.0, but if you let ansible-galaxy
command decide what version, you get 3.6.3:
ansible-galaxy install geerlingguy.php
- downloading role 'php', owned by geerlingguy
- downloading role from https://github.com/geerlingguy/ansible-role-php/archive/3.6.3.tar.gz
- extracting geerlingguy.php to /home/jon/.ansible/roles/geerlingguy.php
- geerlingguy.php (3.6.3) was installed successfully
I only discovered it after attempting to use galaxy to install it. My travis runs for DevShop didn't catch it because it scaffolds up the source code with git first.
I am replicating DrupalVM methods to create @opendevshop containers using https://github.com/geerlingguy/drupal-vm/blob/master/provisioning/requirements.yml
I think this is worth raising with the @ansible/ansible-galaxy team.
Workaround is to modify your requirements.yml
file:
- name: geerlingguy.php
src: https://github.com/geerlingguy/ansible-role-php/archive/3.7.0.tar.gz
See: https://github.com/ansible/galaxy/issues/2116#issuecomment-556137881
Basically, this was a bug in the ansible-galaxy
client in Ansible 2.9.0. Upgrading to Ansible 2.9.1 should fix the issue.
It was causing build failures for every one of my php-related projects for a couple weeks... but now those are resolved, so I am much happier not seeing all those red X's :D
Today, in Packer, we've been getting the following error:
Then it lists every other release of this package. Any idea whatt's wrong. We can't see any changes to the Pipeline.