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 1889908 - IDM unable to delete preserved users
Summary: IDM unable to delete preserved users
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.9
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Simon Pichugin
QA Contact: RHDS QE
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-20 21:27 UTC by Nikhil Suryawanshi
Modified: 2024-10-01 16:59 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-02 04:32:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Nikhil Suryawanshi 2020-10-20 21:27:25 UTC 
Description of problem:

- Unable to delete preserved user, using # ipa user-del command on IPA master.

- Tried to delete the user using #ldapdelete command but it failed with the below error :

===
16/Jul/2020:15:35:16.959781009 -0400] - ERR - parent_update_on_childchange - Parent %s has no children. (op 0x%x, repl_op 0x%x)
 - cn=deleted users,cn=accounts,cn=provisioning,dc=example,dc=com
[16/Jul/2020:15:35:16.967118136 -0400] - ERR - ldbm_back_delete - conn=1331401 op=1 parent_update_on_childchange: old_entry=0x0x560286157200, new_entry=0x(nil), rc=-1
===


Version-Release number of selected component (if applicable):

ipa-server-4.6.8-5

389-ds-base-1.3.10.2-6


Actual results:

- IPA preserved user is still present.

Expected results:

- IPA preserved user should be deleted.
Comment 10 thierry bordaz 2021-03-16 12:52:38 UTC 
	- The entry was moved (MODRDN) to deleted container 30/06/2020:23:05:24
          MODRDN occurred ~5efbc534000200040000 -> 30/06/2020:23:05:24

	- direct deletion (16/Jul/2020:) failed because of
          invalid 'numsubordinates' value of the deleted container (parent entry)
[16/Jul/2020:15:35:16.959781009 -0400] - ERR - parent_update_on_childchange - Parent %s has no children. (op 0x%x, repl_op 0x%x)
 - cn=deleted users,cn=accounts,cn=provisioning,dc=example,dc=com
	  
	- On ipa-1 and ipa2 the 'deleted users' container has tombstoneNumSubordinates: 0
          The only explanation is that a 'deleted users' was DEL (tombstone) and later
          removed by tombstone_trimming.
          DEL of a 'deleted user' looks part of the use case

	- On ipa-1 the 'deleted users' container has no 'numsubordinates'
	  possible explanations are:
		1 The container never had a child - Not possible because of tombstoneNumSubordinates
		2 The container had one unique child that was deleted (tombstone_trimming)
		3 The container had one unique child that was moved out (user_undel)
		4 A bug in 'numsubordinates' management when MODRDN occurred (30/06/2020:23:05:24)
                  reading the code I did not find anything suspicious

	
	in conclusion:
		I think the most probable explanation was 2 or 3
Next:
	- dbscan -f /var/lib/dirsrv/slapd-<inst>/db/<backend>/numsubordinates.db -r
	- Would you confirm the DS version of ipa-1 and ipa-2
		- on June 30th 2020
		- on July 16th 2020
	- Continue investing on scenario 2 and 3
Note You need to log in before you can comment on or make changes to this bug.