RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2046325 - Document that in 8.6 and 9.0, the ipadnsconfig module requires action: member to exclude a global forwarder
Summary: Document that in 8.6 and 9.0, the ipadnsconfig module requires action: member...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: Documentation
Version: 8.6
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Filip Hanzelka
QA Contact: RHEL DPM
Filip Hanzelka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-26 15:42 UTC by Filip Hanzelka
Modified: 2022-05-13 16:02 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
.The `ipadnsconfig` module now requires `action: member` to exclude a global forwarder With this update, excluding global forwarders in Identity Management (IdM) by using the `ansible-freeipa` `ipadnsconfig` module requires using the `action: member` option in addition to the `state: absent` option. If you only use `state: absent` in your playbook without also using `action: member`, the playbook fails. Consequently, to remove all global forwarders, you must specify all of them individually in the playbook. In contrast, the `state: present` option does not require `action: member`.
Clone Of:
Environment:
Last Closed: 2022-01-31 15:37:22 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-109850 0 None None None 2022-01-26 16:02:47 UTC

Description Filip Hanzelka 2022-01-26 15:42:29 UTC
Based on communication from the SME Rafael Jeffman, there is a behavior change in ipadnsconfig affecting docs:

""""
In upcoming RHEL releases (both 8.6 and 9.0) a fix for
ansible-freeipa's ipadnsconfig module has forced a change
in the documented behavior.

The affected sections are 81.8 [1] and 81.9 [1].

The new behavior requires the use of 'action: member' to
exclude a global forwarder. If a user want to keep the current
configuration but "add" (actually ensure presence of) a new
forwarder 'action: member' should also be used.

As neither version is public yet, there is no issue with publicly
available documentation, but there will be a "bug" in the docs
as soon as the new versions are released.

[1]: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_identity_management/managing-dns-forwarding-in-idm_configuring-and-managing-idm#ensuring-the-presence-of-a-dns-global-forwarder-in-idm-using-ansible_managing-dns-forwarding-in-idm
[2]: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_identity_management/managing-dns-forwarding-in-idm_configuring-and-managing-idm#ensuring-the-absence-of-a-dns-global-forwarder-in-idm-using-ansible_managing-dns-forwarding-in-idm
""""

We have agreed that both a release note and an update of the product docs are appropriate: this BZ is to track this effort.


Note You need to log in before you can comment on or make changes to this bug.