#2444 extop request marks dp_req as failed when an entry is not found
Closed: Fixed None Opened 5 years ago by jhrozek.

When a non-existant user is requested with the extop plugin, the dp_request always fails, even if the reason for failure is just that the entry doesn't exist.

Fields changed

component: SSSD => IPA Provider
owner: somebody => sbose

No visible effect, except not filling negative cache.

rhbz: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12.2

We need to do a release as requested by downstream. Moving tickets that are not fixed already or very close to acking to 1.12.3

milestone: SSSD 1.12.2 => SSSD 1.12.3

We don't need to do this ticket in 1.12.3, but it makes sense to implement it in 1.12.x because it's a usability improvement -- makes reviewing the DEBUG logs easier.

mark: => 0
milestone: SSSD 1.12.3 => SSSD 1.12.4

As agreed with Sumit on IRC, it makes sense to implement this ticket in 1.13.

milestone: SSSD 1.12.4 => SSSD 1.13 beta

Fields changed

patch: 0 => 1

milestone: SSSD 1.13 beta => SSSD 1.12.5
resolution: => fixed
status: new => closed

Metadata Update from @jhrozek:
- Issue assigned to sbose
- Issue set to the milestone: SSSD 1.12.5

3 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/3486

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.