Bug 888614 – Failure in memberof can lead to failed database update

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 888614 - Failure in memberof can lead to failed database update

Summary:	Failure in memberof can lead to failed database update

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	sssd (Show other bugs)
Sub Component:
Version:	6.4
Hardware:	Unspecified Unspecified

Priority	high Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Jakub Hrozek
QA Contact:	Kaushik Banerjee
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	895654
	Show dependency tree / graph

Reported:	2012-12-18 21:21 EST by Dmitri Pal
Modified:	2013-02-21 04:42 EST (History)
CC List:	4 users (show)

See Also:
Fixed In Version:	sssd-1.9.2-82.el6
Doc Type:	Bug Fix
Doc Text:	No documentation needed.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2013-02-21 04:42:44 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2013:0508	normal	SHIPPED_LIVE	Low: sssd security, bug fix and enhancement update	2013-02-20 16:30:10 EST

Groups: None (edit)

Description Dmitri Pal 2012-12-18 21:21:03 EST

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

While trying to upgrade to 1.9.x on my RHEL machine I encountred a fatal failure in database upgrade.
The issue was down to a mismatched memberof entry in a user that caused a 'No such attribute' error to be returned when the memberof plugin tried to remove the user entry on upgrade, going from DB version 10 to 11.

Comment 3 Kaushik Banerjee 2013-01-31 10:33:10 EST

Verified in version 1.9.2-82

sssd now starts up fine after the upgrade.

sssd.log shows:
(Thu Jan 31 20:54:15 2013) [sssd] [sysdb_domain_init_internal] (0x0100): Upgrading DB [LDAP] from version: 0.10
(Thu Jan 31 20:54:15 2013) [sssd] [commence_upgrade] (0x0020): UPGRADING DB TO VERSION 0.11
(Thu Jan 31 20:54:15 2013) [sssd] [sysdb_upgrade_10] (0x1000): User [nest_user1] is a member of 1 groups
(Thu Jan 31 20:54:15 2013) [sssd] [sysdb_upgrade_10] (0x0400): Adding ghost [nest_user1] to entry [name=Group_1,cn=groups,cn=LDAP,cn=sysdb]
(Thu Jan 31 20:54:15 2013) [sssd] [sysdb_upgrade_10] (0x0400): Removing fake user [name=nest_user1,cn=users,cn=LDAP,cn=sysdb]
(Thu Jan 31 20:54:15 2013) [sssd] [sysdb_upgrade_10] (0x1000): User [nest_user3] is a member of 2 groups
(Thu Jan 31 20:54:15 2013) [sssd] [sysdb_upgrade_10] (0x0400): Adding ghost [nest_user3] to entry [name=Group_2,cn=groups,cn=LDAP,cn=sysdb]
(Thu Jan 31 20:54:15 2013) [sssd] [sysdb_upgrade_10] (0x0400): Adding ghost [nest_user3] to entry [name=Group_1,cn=groups,cn=LDAP,cn=sysdb]
(Thu Jan 31 20:54:15 2013) [sssd] [sysdb_upgrade_10] (0x0400): Removing fake user [name=nest_user3,cn=users,cn=LDAP,cn=sysdb]
(Thu Jan 31 20:54:15 2013) [sssd] [commence_upgrade] (0x0020): UPGRADING DB TO VERSION 0.12

Comment 4 errata-xmlrpc 2013-02-21 04:42:44 EST

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

Note You need to log in before you can comment on or make changes to this bug.