SSSD / sssd

#96 Startup SBUS race condition
Closed: Fixed Opened by sgallagh.

Closed: Fixed
Reopen Issue

Currently, when monitor clients are started, they open a connection to the monitor during the SBUS initialization prior to entering the mainloop. This means there is the potential for a race condition if the monitor sends the getIdentity response prior to the mainloop being entered and ready to reply to SBUS requests in the client.

It would be better if the SBUS initialization was deferred until after the mainloop starts so that it is guaranteed to be ready to handle requests immediately.

Change how identification works both against monitor and dp

fixedin: => 0.5.0
resolution: => fixed
status: new => closed

Fixed in: 06a3b13134e29b75971970aa45ba14576a4f6ced

Fields changed

rhbz: => 0

Metadata Update from @sgallagh:
- Issue assigned to simo
- Issue set to the milestone: SSSD 0.5.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/1138

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.
Metadata
None
None
None
Normal
defect
SBUS
master
0
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.