Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 875851

Summary:	sysdb upgrade failed converting db to 0.11
Product:	Red Hat Enterprise Linux 6	Reporter:	Jakub Hrozek <jhrozek>
Component:	sssd	Assignee:	Jakub Hrozek <jhrozek>
Status:	CLOSED ERRATA	QA Contact:	Kaushik Banerjee <kbanerje>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	6.4	CC:	dpal, grajaiya, jgalipea, pbrezina
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	sssd-1.9.2-15.el6	Doc Type:	Bug Fix
Doc Text:	No documentation needed.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-21 09:40:11 UTC	Type:	---
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:
Bug Blocks:	881827

Description Jakub Hrozek 2012-11-12 16:52:01 UTC

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/1631

See this thread on sssd-users:
https://lists.fedorahosted.org/pipermail/sssd-users/2012-November/000272.html

It seems we have a bug in the ghost users upgrade code. The only captured debug logs were:
{{{
(Thu Nov  8 16:10:57 2012) [sssd] [sysdb_upgrade_10] (0x0020): UPGRADING DB TO VERSION 0.11
(Thu Nov  8 16:10:57 2012) [sssd] [sysdb_error_to_errno] (0x0020): LDB returned unexpected error: [No such attribute]
}}}

Comment 1 Jakub Hrozek 2012-11-12 16:54:02 UTC

Steps to reproduce:

1. Add a nested group hierarchy to the SSSD 1.8
2. Upgrade to 1.9
3. service sssd start

I'm marking this as a Regression because SSSD fails to start without wiping out the cache after upgrade to 1.9

Credits for finding this issue go to Ondrej Valousek.

Comment 4 Kaushik Banerjee 2012-11-28 16:53:26 UTC

Verified with version sssd-1.9.2-24.el6.x86_64

The following testing steps were followed:
1. Setup sssd(1.8.0-32) on 6.3

2. Lookup a user belonging to a nested group

3. Upgrade to 6.4 (only "yum upgrade sssd") to version 1.9.2-24

4. User and group lookups work fine.


The relevant parts of sssd.log related to sysdb upgrade:

(Wed Nov 28 21:56:28 2012) [sssd] [sysdb_domain_init_internal] (0x0100): Upgrading DB [AD] from version: 0.10
(Wed Nov 28 21:56:28 2012) [sssd] [commence_upgrade] (0x0020): UPGRADING DB TO VERSION 0.11
(Wed Nov 28 21:56:28 2012) [sssd] [ldb] (0x4000): start ldb transaction (nesting: 0)
...
...
(Wed Nov 28 21:56:28 2012) [sssd] [commence_upgrade] (0x0020): UPGRADING DB TO VERSION 0.12
(Wed Nov 28 21:56:28 2012) [sssd] [ldb] (0x4000): start ldb transaction (nesting: 0)
...
...
(Wed Nov 28 21:56:28 2012) [sssd] [sysdb_upgrade_11] (0x1000): Found 0 autofs entries
(Wed Nov 28 21:56:28 2012) [sssd] [ldb] (0x4000): start ldb transaction (nesting: 1)
...
...
(Wed Nov 28 21:56:28 2012) [sssd] [commence_upgrade] (0x0020): UPGRADING DB TO VERSION 0.13
(Wed Nov 28 21:56:28 2012) [sssd] [ldb] (0x4000): start ldb transaction (nesting: 0)
(Wed Nov 28 21:56:28 2012) [sssd] [ldb] (0x4000): start ldb transaction (nesting: 1)
...
...
(Wed Nov 28 21:56:28 2012) [sssd] [commence_upgrade] (0x0020): UPGRADING DB TO VERSION 0.14
(Wed Nov 28 21:56:28 2012) [sssd] [ldb] (0x4000): start ldb transaction (nesting: 0)

Comment 5 errata-xmlrpc 2013-02-21 09:40:11 UTC

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.

http://rhn.redhat.com/errata/RHSA-2013-0508.html