Hide Forgot
Description of problem: a customer was complaining about sss_cache returning 2, ENOENT ( no entries invalidated in the cache ). We believe the error code is valid and quite accurate. But perhaps we will need to document this in the man pages of sss_cache. Or even think about the possibility of always returning 0 since "no entries invalidated" is also successful.
(In reply to German Parente from comment #0) > Or even think about the possibility of always returning 0 since "no entries > invalidated" is also successful. I agree the return code is a bit too strict, that's what I also suggested in the idm-tech thread where this issue was first reported: http://post-office.corp.redhat.com/archives/idm-tech/2018-November/msg00185.html but I couldn't reproduce it locally with a quick test.
Upstream ticket: https://pagure.io/SSSD/sssd/issue/3896
Upstream ticket: https://pagure.io/SSSD/sssd/issue/3919
* master: * 415094687e92789060626176c5ced31d4122692d * 71475f1ed78a65d78f75e5ca0fdc6e20cfdf2f39 * 325df4acae303efeabd96d2247fb5799c728536a * 88c0c3fcd1d97bd499bb28c2065ba19d629fa4f7
* sssd-1-16: * 7983826c3c3736d71bd4447be5f178521b809d64 * 498aaac23db9334ec83de72c8b6c4fbf708120b2 * 0a27a4716adcb2d08e08db3ed719a156691106e7 * 8e6c52f6b043cb4f7b4065ab6a9012a5c1acbf8f
Verified with: [root@qe-blade-09 ~]# rpm -qa sssd sssd-1.16.4-21.el7.x86_64 Verification steps: 1) Remove sssd cache [root@qe-blade-09 ~]# rm -rf /var/lib/sss/db/* 2) Restart sssd [root@qe-blade-09 ~]# systemctl restart sssd 3) Invalidate all groups cache and check return code [root@qe-blade-09 ~]# sss_cache -G [root@qe-blade-09 ~]# echo $? 0 4) Invalidate all users cache and check return code [root@qe-blade-09 ~]# sss_cache -U [root@qe-blade-09 ~]# echo $? 0 5) Invalidate everything and check return code [root@qe-blade-09 ~]# sss_cache -E [root@qe-blade-09 ~]# echo $? 0 Thus from above steps marking this bug as Verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:2177