Learn more about these different git repos.
Other Git URLs
When one has multiple DNS search suffixes listed in /etc/resolv.conf only the first one is used. For example, when using "ldap_uri = ldap://server/" with
search home.domain corp.domain
only server.home.domain is being resolved but not server.corp.domain. In some environments there are geographically distributed servers like server.emea.corp.domain and server.apac.corp.domain so setting just "ldap_uri = ldap://server/" would be preferable (and resolv.conf only contains search for either emea.corp.domain or apac.corp.domain depending on system's current location).
While the above method may not be the best solution for distributing load it is however used in some existing real world environments.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.2.1 owner: somebody => jhrozek
The problem is that we are using ares_query() where we should be using ares_search(). So it is definitely a bug in SSSD, so far I think it will be a simple search-and-replace fix.
ares_query()
ares_search()
status: new => assigned
Replying to [comment:2 jhrozek]:
Sorry, we actually use ares_gethostbyname() which in turn uses ares_search() so the above is not true. However, my scratch c-ares version of host works fine, still investigating.
ares_gethostbyname()
This is not a problem of SSSD but c-ares. Also, this is only problem if you use both "domain" and "search" - AFAIK the semantics is so similar that a workaround might be to just use "search". In this case, c-ares would correctly loop over all search subdomains.
Closing here, if you like you can track the problem in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=597286 or RHEL: https://bugzilla.redhat.com/show_bug.cgi?id=597287
resolution: => invalid status: assigned => closed
Replying to [comment:4 jhrozek]:
Closing here
Simo proposed that we continue to track the issue here since the bug is visible via SSSD. I agree, so reopening.
resolution: invalid => status: closed => reopened
The packages have been build, switching over to Stephen to make sssd.spec require the fixed versions:
- F-12: c-ares-1.6.0-4 (in updates-testing - http://admin.fedoraproject.org/updates/c-ares-1.6.0-4.fc12) - F-13: c-ares-1.7.0-4 (in updates-testing - http://admin.fedoraproject.org/updates/c-ares-1.7.0-4.fc13) - rawhide: c-ares-1.7.1-2 (already there) - EPEL5: c-ares-1.6.0-2 (in updates-testing - http://admin.fedoraproject.org/updates/c-ares-1.6.0-2.el5) - RHEL6: c-ares-1.7.0-3
I didn't bother with F11, it is going EOL and noone has requested a fix.
owner: jhrozek => sgallagh status: reopened => new
This is fixed in the c-ares packages. There are no required changes for SSSD. It doesn't make sense to add specific version requirements on c-ares, as most other features work.
resolution: => wontfix status: new => closed
Metadata Update from @myllynen: - Issue assigned to sgallagh - Issue set to the milestone: SSSD 1.2.1
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/1535
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.