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:
I add a host to a sudorule, then, I add the host to the system, then searching for that host with ipa host-find --in-sudorule=<sudorule> returns zero results

Version-Release number of selected component (if applicable):
ipa-server-2.2.0-2.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. kinit as admin
2. ipa sudorule-add srule
3. ipa sudorule-add-host --hosts=h.testrelm.com srule
4. ipa host-add --ip-address=4.2.2.2 h.testrelm.com
5. ipa host-find --in-sudorule srule
  
Actual results:
[root@ipaqavmc ipa-host-cli]# ipa host-find --in-sudorule srule
---------------
0 hosts matched
---------------
----------------------------
Number of entries returned 0
----------------------------


Expected results:
I expect the search to return h.testrelm.com

Additional info:
I am adding the host to the sudorule before the hosts exists. 

searching for the host if it is added to the sudorule in the correct order works properly.

I do not think this is a bug. When you add a host that's not enrolled in IPA, it is considered as an External host and is also stored in a different LDAP attribute (externalHost) than regular IPA hosts (memberHost with DN to IPA host).

If you use the correct order or remove/add your host to srule, it should be added as a standard IPA host and host-find --in-sudorule will work.

I see no objections, closing as NOTABUG.