#2678 search for a non-sssd user fails the request and logs a confusing error message
Closed: Fixed None Opened 5 years ago by jhrozek.

This bug doesn't really affect functionality, but produces error messages that confuse users. When a non-SSSD user is requested, the back end request fails:

(Sun Jun 14 06:50:08 2015) [sssd[be[4gjn.prv]]] [groups_by_user_done] (0x0040): Failed to canonicalize name, using [postfix].
(Sun Jun 14 06:50:08 2015) [sssd[be[4gjn.prv]]] [sysdb_set_entry_attr] (0x0080): ldb_modify failed: [No such object](32)[ldb_wait: No such object (32)]
(Sun Jun 14 06:50:08 2015) [sssd[be[4gjn.prv]]] [set_initgroups_expire_attribute] (0x0020): Failed to set initgroups expire attribute
(Sun Jun 14 06:50:08 2015) [sssd[be[4gjn.prv]]] [ipa_id_get_account_info_orig_done] (0x0040): sdap_handle_acct request failed: 2

Since the user is just not found, we should end the request gracefully and return control to the responder.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 backlog

Fields changed

owner: somebody => lslebodn
patch: 0 => 1
status: new => assigned

resolution: => fixed
status: assigned => closed

Fields changed

rhbz: => todo

Do we really need a bugzilla ticket for changed debug message?

Fields changed

rhbz: todo => 0

Metadata Update from @jhrozek:
- Issue assigned to lslebodn
- Issue set to the milestone: SSSD 1.13 backlog

3 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3719

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.