Bug #23288
closed
galaxy import job put roles in ~user/.ansible/roles while UI Import expects roles to be in /etc/ansible/roles
Added by Lukas Pramuk over 6 years ago.
Updated almost 4 years ago.
Description
For import to work the roles gotta be in /etc/ansible/roles
vs.
Ansible Galaxy import job put them under ~user/.ansible/roles
(regression since this was already working)
foreman-1.18.0-0.develop.201804091403git41fe8c6.el7.noarch
katello-3.7.0-1.nightly.el7.noarch
tfm-rubygem-foreman_ansible-2.0.4-1.fm1_18.el7.noarch > updated to foreman_ansible (2.1.0)
tfm-rubygem-foreman_ansible_core-2.0.2-1.fm1_18.el7.noarch
rubygem-smart_proxy_ansible-2.0.2-3.fm1_18.el7.noarch
ansible-2.5.0-2.el7.noarch
You are right, the default import path for ansible-galaxy install command has changed. The initial driver for change was that regular users do not have write access to /etc/ansible/roles, so the command is broken for them by default. There are 2 ways users can deal with the default path change:
1) users can do 'ansible-galaxy install owner.role -p /etc/ansible/roles'
2) users can add ~/.ansible/roles into roles_path in ansible.cfg
Is there any specific change you would like to see to resolve this issue?
I mean REX Galaxy Import job puts roles elsewhere than Import Roles looks after them.
REX job should put roles where import expects them otherwise this type of "out-of-box" job is then useless.
- Related to Bug #31488: Install Roles from Galaxy' does not honor the location input
added
- Status changed from New to Ready For Testing
- Assignee set to Ondřej Ezr
- Pull request https://github.com/theforeman/foreman_ansible/pull/373 added
- Status changed from Ready For Testing to Closed
Also available in: Atom
PDF