search

freeipa / ansible-freeipa

Ansible roles and modules for FreeIPA
GNU General Public License v3.0
505 stars 231 forks source link

what is the best workaround for ansible bug #68361 ? #315

Closed RobVerduijn closed 3 years ago

RobVerduijn commented 4 years ago

Hello,

After trying to install freeipa server with the ansible-freeipa collection for a couple days I found out I was being bitten by this bug: https://github.com/ansible/ansible/issues/68361

You obviously already know this one and you can't help it because it is an ansible bug, Since it seems that this one is going to take a while before it is applied in a stable release (or backported to 2.9) what would you recommend as a workaround for this one ? (besides manually applying the patch mentioned in the post)

Rob

t-woerner commented 4 years ago

Ansible 2.10 should provide a fix for this issue. I have not been able to test this though.

t-woerner commented 4 years ago

A possible workaround for now is to install ipa-server packages also on the controller. Then ansible is able to load the module_utils plugins on the controller to find out what needs to be transferred to the node. The version of ipa-server packages should not matter as long as it is a supported IPA version.

t-woerner commented 4 years ago

Only the collection is affected by this. You can use the RPM that is part of RHEL-8 and Fedora. It is installing the roles and plugins into the default ansible locations for roles and plugins. You can also use the roles and plugins from the ansible-freeipa releases this way. Please have a look at https://github.com/freeipa/ansible-freeipa#how-to-use-ansible-freeipa and ignore the galaxy section there.

RobVerduijn commented 4 years ago

Thanx,

I'll definitely consider your suggestions and which one to use. Let's hope ansible 2.10 doesn't mis it's roadmap release date by much, which is next month https://docs.ansible.com/ansible/devel/roadmap/ROADMAP_2_10.html

Rob

RobVerduijn commented 4 years ago

This bug is back again

Rob

rjeffman commented 3 years ago

@RobVerduijn, the bug never gone away. It is an Ansible 2.9 issue with collections.