-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
what is the best workaround for ansible bug #68361 ? #315
Comments
Ansible 2.10 should provide a fix for this issue. I have not been able to test this though. |
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. |
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. |
Thanx, I'll definitely consider your suggestions and which one to use. Rob |
This bug is back again Rob |
@RobVerduijn, the bug never gone away. It is an Ansible 2.9 issue with collections. |
* prevents failures on Ansible 2.9 during module build due to ansible/ansible#68361 * fixes freeipa#315
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:
ansible/ansible#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
The text was updated successfully, but these errors were encountered: