You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
downloading role 'project_deploy_module', owned by -%20src%3A%20f500
Sorry, - src: f500.project_deploy_module was not found on galaxy.ansible.com.
downloading role '-%20name%3A%20ntp', owned by
Sorry, - name: ntp was not found on galaxy.ansible.com.
downloading role 'ntp', owned by src%3A%20resmo
Sorry, src: resmo.ntp was not found on galaxy.ansible.com.
downloading role '-%20name%3A%20logrotate', owned by
Sorry, - name: logrotate was not found on galaxy.ansible.com.
downloading role 'logrotate', owned by src%3A%20nickhammond
Sorry, src: nickhammond.logrotate was not found on galaxy.ansible.com.
downloading role '-%20name%3A%20php5-xdebug', owned by
Sorry, - name: php5-xdebug was not found on galaxy.ansible.com.
downloading role 'php5-xdebug', owned by src%3A%20MaximeThoonsen
Sorry, src: MaximeThoonsen.php5-xdebug was not found on galaxy.ansible.com.'
However, I am able to install the roles manually through:
Judging from the errors it seems like your Ansible doesn't like the requirements.yml format which leads me to believe it's an issue with your Ansible version.
What version are you running? We require at least 1.8 now.
Scott, spot on, sorry I missed this, as I thought my installation was pulling from the ansible ppa, looks like it was not and instead I am installed off the OS repo (v1.7.2). Thanks for your time brother. And thank you for creating such a wonderful software!
When attempting to install the ansible galaxy I get the following output
ansible-galaxy install -r requirements.yml -p vendor/roles
However, I am able to install the roles manually through:
ansible-galaxy install f500.project_deploy_module -p vendor/roles
I went in and manually renamed the folders to what is specified in the
requirements.yml
Not sure what is causing this. But I believe I am able to run without it now.
The text was updated successfully, but these errors were encountered: