Bug 1661182
| Summary: | sss_cache prints spurious error messages when invoked from shadow-utils on package install | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Jakub Hrozek <jhrozek> |
| Component: | sssd | Assignee: | Tomas Halman <thalman> |
| Status: | CLOSED ERRATA | QA Contact: | Anuj Borah <aborah> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.0 | CC: | aborah, apeetham, dbula, grajaiya, jhrozek, lslebodn, mzidek, pbrezina, sgoveas, thalman, tscherf |
| Target Milestone: | rc | ||
| Target Release: | 8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | sssd-2.1.0-1.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1659656 | Environment: | |
| Last Closed: | 2019-11-05 22:33:53 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1659656, 1682305 | ||
| Bug Blocks: | |||
|
Description
Jakub Hrozek
2018-12-20 10:29:15 UTC
Upstream ticket: https://pagure.io/SSSD/sssd/issue/3919 * master: * 415094687e92789060626176c5ced31d4122692d * 71475f1ed78a65d78f75e5ca0fdc6e20cfdf2f39 * 325df4acae303efeabd96d2247fb5799c728536a * 88c0c3fcd1d97bd499bb28c2065ba19d629fa4f7 Additional fixes: * master: * 159a2316b8d5560da5264022c598f1072f21bdba * 2de3c5fb2490da0dabed0de498a8296db85a1e61 * sssd-1-16: * 6c8084778fa5450b07b437ecf72cae247767b9d6 * 3ec716bb042dc51ae7a75e546c64c8e89c1a2d80 Verified the bug on SSSD Version : sssd-2.2.0-16.el8.x86_64 Steps followed during verification: 1. Reproduce the issue with older build, for example install sssd-2.0.0-6.el8.x86_64 and verify step 2. 2. Test a scenario wherein SSSD have never been started but some utilities in shadow-utils call sss_cache. So stop SSSD service and delete cache files from /var/lib/sss/db/ dir and execute the following: # sss_cache -U ; echo $? (Wed Aug 28 03:42:26:575405 2019) [sss_cache] [confdb_get_domains] (0x0010): No domains configured, fatal error! Could not open available domains 2 # sss_cache -G ; echo $? (Wed Aug 28 03:42:50:940325 2019) [sss_cache] [confdb_get_domains] (0x0010): No domains configured, fatal error! Could not open available domains 2 # sss_cache -E ; echo $? (Wed Aug 28 03:42:58:567361 2019) [sss_cache] [confdb_get_domains] (0x0010): No domains configured, fatal error! Could not open available domains 2 3. The above commands log "fatal error" which infact is not that fatal. In such scenarios, sss_cache shouldn't fail or log extreme messages. Now upgrade SSSD to latest version ie sssd-2.2.0-16 and run some sss_cache tests. 4. Scenario-1: when SSSD is inactive and db files don't exist, run sss_cache command for invalidating entries. # sss_cache -U ; echo $? 0 # sss_cache -G ; echo $? 0 # sss_cache -E ; echo $? 0 # sss_cache -u non-existinguser ; echo $? 0 NOTE: As expected, fatal error is not logged. 5. Scenario-2: when SSSD is active however entries does not exist in cache. # sss_cache -U ; echo $? 0 # sss_cache -G ; echo $? 0 # sss_cache -E ; echo $? 0 # sss_cache -u non-existinguser ; echo $? No cache object matched the specified search 2 NOTE: As expected, no fatal errors and command only fails when non existing entries are invalidated. 6. Scenario-3: when SSSD is active and a non-existing domain is invalidated. # sss_cache -d nonexisting -g TEST ; echo $? Could not open domain nonexisting. If the domain is a subdomain (trusted domain), use fully qualified name instead of --domain/-d parameter. 2 OBSERVATION: Tests show expected results. 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:3651 |