Bug 868121
| Summary: | sss_cache says 'Wrong DB version' | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Stef Walter <stefw> |
| Component: | sssd | Assignee: | Jakub Hrozek <jhrozek> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | jhrozek, sbose, sgallagh, ssorce |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-01-12 00:10:40 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: | |||
|
Description
Stef Walter
2012-10-19 05:40:49 UTC
Upstream ticket: https://fedorahosted.org/sssd/ticket/1589 The domains are upgraded automatically when the SSSD is started after being upgraded to a package version that uses a newer internal DB version. Is it possible that you had a domain configured with an old SSSD version, then unconfigured it while the cache was still on the dist, upgraded the SSSD and then ran the sss_cache tool? btw if you can still reproduce the bug, here's how you can inspect which database has the wrong db version: for db in /var/lib/sss/db/cache_*; do echo === DB: $db ===; ldbsearch -H $db cn=sysdb version; done ldbsearch is a part of ldb-tools. The other reason might be that the cache upgrade really failed -- that would be indicated by a very loud DEBUG message in the logs. AH, sorry, I was reading the error backwards. The sss_cache was complaining that the database was NEWER than expected. The 0.11 version is pre-1.9. Can you check what version of sssd-tools you had that produced the error? (sss_cache is still part of sssd-tools, not sssd even though there is a bug to change it) Here you go: Name : sssd-tools Arch : x86_64 Version : 1.9.2 Release : 1.fc18 Size : 560 k It's likely that I did alternate old and new sssd versions, although don't ask me when and which ones :) OK, I was playing with sss_cache and trying to break it, but couldn't along my colleague Michal who is fixing and breaking the command line tools all the time :-). Given that the only way we could reproduce the error message was by really trying to load a newer db version with an old version of the SSSD, we're going to just improve the error message upstream. Currently it's cryptic and scary. sssd-1.9.3-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/sssd-1.9.3-1.fc18 Package sssd-1.9.3-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing sssd-1.9.3-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-19960/sssd-1.9.3-1.fc18 then log in and leave karma (feedback). sssd-1.9.3-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |