Learn more about these different git repos.
Other Git URLs
In some cases, when sssd starts before the network does, the sss_be is already marked as offline due to previous request hitting it already.
But when the network comes up, we should be notified via the change to resolv.conf (where we have an inotify watch) and via libnl callbacks.
We should investigate the downstream reports and this ticket was filed precisely to track that.
Metadata Update from @jhrozek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1406678
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.16.0
Metadata Update from @jhrozek: - Issue priority set to: minor
Since we are required to release a new upstream tarball no later than Friday Oct-20, I'm moving tickets that will not be closed by that date to the next milestone, 1.16.1
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.16.1 (was: SSSD 1.16.0)
I really think we should listen to NM D-Bus interface if it's available..
Metadata Update from @jhrozek: - Issue tagged with: postpone-to-2-0
Metadata Update from @jhrozek: - Issue untagged with: postpone-to-2-0 - Issue set to the milestone: SSSD 2.0 (was: SSSD 1.16.1)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.1 (was: SSSD 2.0)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)
Commit fe42880 fixes this issue
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/4493
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.