(Tue Aug 9 07:50:13 2011) [sssd] [sysdb_domain_init_internal] (4): Upgrading DB [redhat.com] from version: 0.5 (Tue Aug 9 07:50:13 2011) [sssd] [sysdb_upgrade_05] (0): UPGRADING DB TO VERSION 0.6 (Tue Aug 9 07:50:13 2011) [sssd] [ldb] (9): start ldb transaction (nesting: 0) (Tue Aug 9 07:50:13 2011) [sssd] [ldb] (9): start ldb transaction (nesting: 1) (Tue Aug 9 07:50:13 2011) [sssd] [ldb] (9): tevent: Added timed event "ltdb_callback": 0x2381010 (Tue Aug 9 07:50:13 2011) [sssd] [ldb] (9): tevent: Added timed event "ltdb_timeout": 0x2381c70 (Tue Aug 9 07:50:13 2011) [sssd] [ldb] (9): tevent: Destroying timer event 0x2381c70 "ltdb_timeout" (Tue Aug 9 07:50:13 2011) [sssd] [ldb] (9): tevent: Ending timer event 0x2381010 "ltdb_callback" (Tue Aug 9 07:50:13 2011) [sssd] [ldb] (9): cancel ldb transaction (nesting: 1) (Tue Aug 9 07:50:13 2011) [sssd] [ldb] (9): cancel ldb transaction (nesting: 0) (Tue Aug 9 07:50:13 2011) [sssd] [sysdb_domain_init_internal] (0): Unknown DB version [0.5], expected [0.7] for domain redhat.com! Aborted (core dumped)
Fields changed
component: SSSD => SysDB owner: somebody => sgallagh status: new => assigned
Turns out this isn't a bug. It was a side-effect of manual edits I'd made to my database.
I tested upgrades from a pristine 1.5.x sysdb to 1.6.x and it worked fine.
resolution: => invalid status: assigned => closed
rhbz: => 0
Metadata Update from @sgallagh: - Issue assigned to sgallagh - Issue set to the milestone: SSSD 1.6.1
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/2000
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.