#3257 sudo: do not store usn if no rules are found
Closed: Fixed None Opened 4 years ago by pbrezina.

The patch that fixed #2970 is not complete and does not handle the case when ldap doesn't contain any sudorule during the initial full refresh -- usn is then set to 1 instead of remaining unset and we are trying to search modifyTimestamp>=1 during smart refresh which doesn't return any result.

This is a regression caused by IPA schema patches which was supposed to be fixed by #2970, but the fix was apparentely not complete.


Fields changed

owner: somebody => pbrezina
patch: 0 => 1
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=1399589 1399589]
status: new => assigned

milestone: NEEDS_TRIAGE => SSSD 1.13.5
resolution: => fixed
status: assigned => closed

Metadata Update from @pbrezina:
- Issue assigned to pbrezina
- Issue set to the milestone: SSSD 1.13.5

4 years 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/4290

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.

Login to comment on this ticket.

Metadata