#1436 LOCAL domain lookups don't work
Closed: Fixed None Opened 10 years ago by jhrozek.

Even though we are not getting segfaults anymore, lookups in a local domain do not work:

(Mon Jul 23 16:45:28 2012) [sssd[nss]] [accept_fd_handler] (0x0400): Client connected!
(Mon Jul 23 16:45:28 2012) [sssd[nss]] [sss_cmd_get_version] (0x0200): Received client version [1].
(Mon Jul 23 16:45:28 2012) [sssd[nss]] [sss_cmd_get_version] (0x0200): Offered version [1].
(Mon Jul 23 16:45:28 2012) [sssd[nss]] [sss_parse_name_for_domains] (0x0200): name 'lcltest' matched without domain, user is lcltest
(Mon Jul 23 16:45:28 2012) [sssd[nss]] [nss_cmd_getpwnam] (0x0100): Requesting info for [lcltest] from [<ALL>]
(Mon Jul 23 16:45:28 2012) [sssd[nss]] [sss_dp_issue_request] (0x0400): Issuing request for [0x42e450:domains@local]
(Mon Jul 23 16:45:28 2012) [sssd[nss]] [sss_dp_get_domains_msg] (0x0400): Sending get domains request for [local][not forced][]
(Mon Jul 23 16:45:28 2012) [sssd[nss]] [sss_dp_internal_get_send] (0x0020): BUG: The Data Provider connection for local is not available!(Mon Jul 23 16:45:28 2012) [sssd[nss]] [sss_dp_issue_request] (0x0020): The request has disappeared?
(Mon Jul 23 16:45:28 2012) [sssd[nss]] [client_recv] (0x0200): Client disconnected!

This is a regression, setting blocker severity.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.0

Fields changed

rhbz: => 0

Fields changed

milestone: SSSD 1.9.0 => SSSD 1.9.0 RC1

Fields changed

owner: somebody => pbrezina
status: new => assigned

Fields changed

patch: 0 => 1

master: bdbf4f1

proposed_priority: => Blocker
resolution: => fixed
status: assigned => closed

Metadata Update from @jhrozek:
- Issue assigned to pbrezina
- Issue set to the milestone: SSSD 1.9.0 beta 7

5 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/2478

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.