Learn more about these different git repos.
Other Git URLs
Fix lookup_netgr_step() respectively subsequently called check_cache not to access result of sysdb_getnetgr() in case of ENOENT is returned.
Accessing output parameters of function which didn't returned EOK is dangerous practice.
Not to block completely efforts on 1991 for the time being 'save' result is returned even if return value is ENOENT.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.13 beta rhbz: => 0
mark: => 0
milestone: SSSD 1.13 beta => SSSD 1.13 backlog priority: major => minor
Mass-moving tickets not planned for the next two releases.
Please reply with a comment if you disagree about the move..
milestone: SSSD 1.13 backlog => SSSD 1.15 beta
Metadata Update from @preichl: - Issue marked as blocked by: #1991 - Issue set to the milestone: SSSD Future releases (no date set yet)
Metadata Update from @thalman: - Custom field blocking reset (from 1991) - Custom field design_review adjusted to on (was: 0) - Custom field mark adjusted to on (was: 0) - Custom field patch adjusted to on (was: 0) - Custom field review adjusted to on (was: 0) - Custom field sensitive adjusted to on - Custom field testsupdated adjusted to on (was: 0) - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
No longer relevant due to switch to cache_req.
Metadata Update from @pbrezina: - Custom field blocking adjusted to 1991 - Issue marked as blocking: #1991 - Issue status updated to: Open (was: Closed)
Metadata Update from @pbrezina: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
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/3423
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.