Learn more about these different git repos.
Other Git URLs
In the current implementation the event that encounters a sink that is connecting to its data storage will not skip this sink but rather retry this sink later when sink is expected to be ready. It is not going to skip the sink hoping that sink would successfully connect. It will just reschedule itself to come back when the time for the sink to get connected elapses. However there might be sinks that in this case should be skipped and not waited for. Thus there should be a configuration flag that would allow configuring this option on per sink basis.
This should come with official ELAPI 1.0 release that would be some time before 1.2.
Fields changed
milestone: SSSD Deferred => SSSD 1.2
THE ISSUE IS MOVED INTO ELAPI TRAC INSTANCE.
resolution: => wontfix status: new => closed
Metadata Update from @dpal: - Issue assigned to dpal - Issue set to the milestone: SSSD 1.2.0
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/1379
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.