Thomas Woerner
Thomas Woerner
Fixed with https://github.com/freeipa/ansible-freeipa/pull/1229
IPA-Client-Test FAILED! => {"changed": false, "msg": "Failed to verify that xxx xxx is an IPA Server
`ipaclient_servers=ipaserver1.example.com,ipaserver2.example.com` A comma should fix your issue. ^^^
IPA-Client-Test FAILED! => {"changed": false, "msg": "Failed to verify that xxx xxx is an IPA Server
@abbra I think we should enforce the exact (major?) version of python3-cryptography for new ipa builds to prevent this.
There are more places where getattr(context, 'principal') is used in plugins. Would it be good to fix them too?
For the enablement of batch command in the IpaAnsibleModule backend for client context we would need to have a way to detect the availability of this PR on the server...
@abbra I think it would be good to add an option to the existing batch command. Something that might help for ansible-freeipa would be to have some sort of a...
The only field that ansible-freeipa modules are currently using from the batch results is `randompassword` for user and host modules. It would be great if we could limit the output...
LGTM keeponly works like a charm.
Yes, this fixes the issue for me. I think it might be good to have a test in FreeIPA for this.
The role should be able to keep settings that are not changed like for example mount points, labels, etc. while you are resizing a filesystem. It should not expect that...