#4125 files_provider: race condition
Closed: cloned-to-github a year ago by pbrezina. Opened a year ago by atikhonov.

Schematically files_provider mode of operation is as following:
1. DB file is changed
2. inotify callback is triggered in SSSD
3. Cache is updated to reflect change of DB file

Between (1) and (2) SSSD (libnss_sss.so) returns stale data.

More details can be found in the comments of PR947


@atikhonov is there anything more to be done?

Metadata Update from @thalman:
- Issue tagged with: Canditate to close

a year ago

@atikhonov is there anything more to be done?

Not sure I understand the question.
To the best of my knowledge, nothing was done yet wrt this ticket.

Or do you ask if there is other known problems with files provider? (yes, there are)

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

a year ago

Well, from my point of view, "files" provider, being offered as a replacement for libnss_files, should not regress usability.

I see this bug as a such regression, so I think it is important to fix (if stance "files provider is the default" is kept).

Metadata Update from @pbrezina:
- Custom field design_review adjusted to on
- Custom field mark adjusted to on
- Custom field patch adjusted to on
- Custom field review adjusted to on
- Custom field sensitive adjusted to on
- Custom field testsupdated adjusted to on
- Issue status updated to: Open (was: Closed)

a year ago

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/5086

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 Update from @pbrezina:
- Issue close_status updated to: cloned-to-github
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata