#1517 subdomain discovery is too noisy
Closed: Fixed None Opened 11 years ago by jhrozek.

When the SSSD is used with a back end that does not support subdomains, the debug messages get too noisy for no reason:

[sssd[nss]] [sss_dp_issue_request] (0x0400): Issuing request for [0x43ae00:domains@redhat.com]
[sssd[nss]] [sss_dp_get_domains_msg] (0x0400): Sending get domains request for [redhat.com][not forced][]
[sssd[nss]] [sss_dp_internal_get_send] (0x0400): Entering request [0x43ae00:domains@redhat.com]
[sssd[be[redhat.com]]] [be_get_subdomains] (0x0400): Got get subdomains [not forced][]
[sssd[be[redhat.com]]] [be_get_subdomains] (0x0100): Undefined backend target.
[sssd[be[redhat.com]]] [be_get_subdomains] (0x1000): Request processed. Returned 3,19,Subdomains back end target is not configured
[sssd[nss]] [sss_dp_get_reply] (0x1000): Got reply from Data Provider - DP error code: 3 errno: 19 error message: Subdomains back end target is not configured

We could do one of the following:
1. create a dummy subdomain provider that will just shortcut and use it for all back ends other than IPA
2. just be less noisy in other back ends


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.0
rhbz: => 0
type: defect => task

Fields changed

owner: somebody => sbose

Fields changed

patch: 0 => 1

fixed in c3f2743

resolution: => fixed
status: new => closed

Metadata Update from @jhrozek:
- Issue assigned to sbose
- Issue set to the milestone: SSSD 1.9.0

7 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/2559

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.

Metadata