[description of the issue]
The fix for #8044 in commit 9fe984f replaced the LDAP_NO_SUCH_OBJECT error code at two places where it was actually correct. As a result lookups for UIDs or GIDs will return the generic LDAP_OPERATIONS_ERROR to clients if the UID or GID is coming from a different domain than the requested. Since the given UID or GID does not exists in the domain LDAP_NO_SUCH_OBJECT is the right return code and would help the client to act accordingly.

Steps to Reproduce

1. Setup IPA with trust to AD
2. Set the domain resolution order so that the trusted AD domain is looked up first
3. On an IPA client call getent passwd UID_of_an_IPA_user or getent group GID_Of-IPA_group

Actual behavior

With debug_level = 9 in the sssd_nss.log messages like Data Provider Error: 3, 1432158230, Network I/O Error and in the backend log messages like ldap_extended_operation result: Operations error(1), Failed to handle the request. can be seen.

Expected behavior

Nss responder and backend log should just indicate that the given UID or GID is not present in the given domain.

Version/Release/Distribution

ipa-4.6 and above, all versions where fox for #8044 was applied.