If InfoPipe is activate via DBus the initial request which activate the responder is not answered properly at least for some request types:
[root@f25 ~]# systemctl stop sssd.service ; rm -f /var/log/sssd/* ; rm -f /var/lib/sss/db/* ; systemctl start sssd.service [root@f25 ~]# dbus-send --system --print-reply --dest=org.freedesktop.sssd.infopipe /org/freedesktop/sssd/infopipe/Users org.freedesktop.sssd.infopipe.Users.ListByName string:"cu*" uint32:10 Error org.freedesktop.DBus.Error.Failed: Failed to fetch users by filter [1432158244]: Domain not found
Wait for about 10s to pass the negative cache
[root@f25 ~]# dbus-send --system --print-reply --dest=org.freedesktop.sssd.infopipe /org/freedesktop/sssd/infopipe/Users org.freedesktop.sssd.infopipe.Users.ListByName string:"cu*" uint32:10 method return time=1493735649.100701 sender=:1.1985 -> destination=:1.1986 serial=7 reply_serial=2 array [ object path "/org/freedesktop/sssd/infopipe/Users/ChIlD_2ead_2edevel/1296801104" object path "/org/freedesktop/sssd/infopipe/Users/ChIlD_2ead_2edevel/1296801105" ]
I can see the same when looking up users by certificate. My guess is that the InfoPipe responder might not be initialized properly, maybe the initial sub-domain request to the backend is not finished and hence the responder does not know about the available domains?
Metadata Update from @fidencio: - Issue assigned to fidencio
Metadata Update from @lslebodn: - Custom field version adjusted to 1.15.1
Metadata Update from @fidencio: - Custom field patch adjusted to on
PR: https://github.com/SSSD/sssd/pull/259
Metadata Update from @jhrozek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1447098
Issue linked to Bugzilla: Bug 1447098
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.15.3
Metadata Update from @jhrozek: - Issue priority set to: major
master: * 1a89fc33d1b9b1070c7ab83fb0314e538ac46736
Metadata Update from @lslebodn: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
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/4414
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.