Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:
Via the IdM Web UI, a sudo rule can be constructed that specifies the rule should apply to the "ipaservers" host group.  However, because this group does not have a matching nisNetGroup, the sudo rule will not provide the expected access.  Running the sudo command on one of the servers in the ipaservers group will simply result in a failure.

Version-Release number of selected component (if applicable):
RHEL 7,4
ipa-server-4.5.0-21.el7_4.2.2.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Create a sudo rule that specifies "ipaservers" in the "Access this host: Host Groups" section
2. SSH into an IPA server (member of "ipaservers" group) as a user affected by that sudo rule
3. Attempt to use sudo command (e.g., 'sudo -l') and see failure.
4. Change rule from "ipaservers" to any other group, or explicitly listing specific individual servers, or simply "Any Host", and 'sudo -l' succeeds.

Actual results:
sudo on client fails

Expected results:
sudo should succeed

Additional info:
Discussion on Red Hat internal idm list Nov 22

Upstream ticket:
https://pagure.io/freeipa/issue/7284

Will this issue be addressed soon?

--
There is no plan, priority or team capacity now or in the near future for a Red Hat engineer to work on this request. Thus, i am closing the ticket as wontfix or upstream (in case there is an upstream ticket that the community can help us solve). 

We might revisit this decision according to our product goals. Ping tapazogl / Theo in GChat if you need any further clarification. Thank you for reporting this bug/feature.
---