Updated network ipaclient network settings do not propagate #1128
Labels
Comments
|
The deployment roles are not idempotent, you should not re-run the playbook to update settings. Did the deployment failed and you had to try it again? If that's the case, you should "undeploy" and then deploy it again. If it is to change the settings on a fully deployed IPA client, I'd suggest using some plugin that deal with Network Manager, as the network Linux System Role |
|
For ipaclient role, you can enable |
|
Yes, we do have |
|
It seems you found a bug. |
t-woerner
added a commit
to t-woerner/ansible-freeipa
that referenced
this issue
Apr 22, 2024
The method execute_ipa_commands has been extended to handle multi
commands with the batch command.
New parameters have been added to execute_ipa_commands:
batch: bool
Enable batch command use to speed up processing
batch_size: integer
Maximum mumber of commands processed with the batch command
debug: integer
Enable debug output for the exection. 0x1 is the command list,
0x10 is the batch number and batch size
Batch mode can be enabled within the module with setting batch to True
for execute_ipa_commands.
Fixes: freeipa#1128 (batch command support)
t-woerner
added a commit
to t-woerner/ansible-freeipa
that referenced
this issue
Apr 24, 2024
The method execute_ipa_commands has been extended to handle multi
commands with the batch command.
New parameters have been added to execute_ipa_commands:
batch: bool
Enable batch command use to speed up processing
batch_size: integer
Maximum mumber of commands processed with the batch command
debug: integer
Enable debug output for the exection. 0x1 is the command list,
0x10 is the batch number and batch size
Batch mode can be enabled within the module with setting batch to True
for execute_ipa_commands.
Fixes: freeipa#1128 (batch command support)
t-woerner
added a commit
to t-woerner/ansible-freeipa
that referenced
this issue
May 13, 2024
The method execute_ipa_commands has been extended to handle multi
commands with the batch command.
New parameters have been added to execute_ipa_commands:
batch: bool
Enable batch command use to speed up processing
batch_size: integer
Maximum mumber of commands processed with the batch command
debug: integer
Enable debug output for the exection. 0x1 is the command list,
0x10 is the batch number and batch size
Batch mode can be enabled within the module with setting batch to True
for execute_ipa_commands.
Fixes: freeipa#1128 (batch command support)
t-woerner
added a commit
to t-woerner/ansible-freeipa
that referenced
this issue
May 21, 2024
The method execute_ipa_commands has been extended to handle multi
commands with the batch command.
New parameters have been added to execute_ipa_commands:
batch: bool
Enable batch command use to speed up processing
batch_size: integer
Maximum mumber of commands processed with the batch command
debug: integer
Enable debug output for the exection. 0x1 is the command list,
0x10 is the batch number and batch size
Batch mode can be enabled within the module with setting batch to True
for execute_ipa_commands.
Fixes: freeipa#1128 (batch command support)
|
That was the wrong issue :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When updating the ipaclient settings, e.g. adding another DNS server, and rerunning the playbook, the updated settings aren't applied. The reason seems to be that ansible-freeipa only checks that the file
/etc/NetworkManager/conf.d/zzz-ipa.confexists and not that the contents reflect the variables defined in ansible. E.g. for the DNS setting,ansible-freeipa/roles/ipaclient/library/ipaclient_configure_dns_resolver.py
Line 198 in cf779e4
(IIRC we saw the same issue with some other setting (DNS domain maybe), so it's not only the list of DNS servers, but I no longer remember exactly what it was)
The text was updated successfully, but these errors were encountered: