#3896 sss_cache shouldn't return ENOENT when no entries match
Closed: duplicate 2 years ago by jhrozek. Opened 2 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1653759

Description of problem:

a customer was complaining about sss_cache returning 2, ENOENT ( no entries
invalidated in the cache ).

Or even think about the possibility of always returning 0 since "no entries
invalidated" is also successful.

German said he reproduced this easily:
Well, I have reproduced very easily like this:

=======================
[root@ipatrust ~]# rm -rf /var/lib/sss/db/* 

[root@ipatrust ~]# systemctl restart sssd.service

[root@ipatrust ~]# sss_cache -G
No cache object matched the specified search

[root@ipatrust ~]# echo $?
2


[root@ipatrust ~]# sss_cache -U
No cache object matched the specified search

[root@ipatrust ~]# echo $?
2

This seems to be expected return "no entries" when there's nothing to invalidate.

Now:

[root@ipatrust ~]# id gparente
uid=142600006(gparente) gid=142600006(gparente) groups=142600006(gparente),142600015(newgroup)

[root@ipatrust ~]# sss_cache -U
[root@ipatrust ~]# echo $?
0

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1653759

2 years ago

Metadata Update from @jhrozek:
- Issue tagged with: bug, easyfix

2 years ago

CC @atikhonov this one might be interesting for you (not urgent though)

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.1

2 years ago

This turns out to be a duplicate of #3919 (it might be confusing to close if favour of a new bug, but in this case, the newer bug is linked with a more descriptive RHBZ and we can just relink the RHBZ this ticket is linked with to #3919)

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

2 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/4881

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