Bug 1859215

Summary:	lib389 Issue: With Accounts/Account module delete fuction is not working
Product:	Red Hat Directory Server	Reporter:	mreynolds
Component:	389-ds-base	Assignee:	Simon Pichugin <spichugi>
Status:	CLOSED ERRATA	QA Contact:	RHDS QE <ds-qe-bugs>
Severity:	unspecified	Docs Contact:	Marc Muehlfeld <mmuehlfe>
Priority:	unspecified
Version:	11.0	CC:	aadhikar, pasik, sgouvern, spichugi, vashirov
Target Milestone:	---	Flags:	spichugi: needinfo+
Target Release:	dirsrv-11.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	sync-to-jira
Fixed In Version:	redhat-ds-11-8030020210304204141-0b92cc7b	Doc Type:	Bug Fix
Doc Text:	.The `lib389` library no longer fails to delete entries discovered by the `Account` object Previously, the `_protected` flag of the `Account` object in the `lib389` Directory Server library was enabled. As a consequence, `delete` operations failed. This update sets the flag to `False`. As a result, the library no longer fails if you delete or rename entries discovered by the `Account` object.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-04-19 09:54:31 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:

Description mreynolds 2020-07-21 13:28:57 UTC

This bug is created as a clone of upstream ticket:
https://pagure.io/389-ds-base/issue/51074

Try to create some user with either UserAccounts Or Accounts Or try to generate users with dbgen . Then try to delete them with Accounts. 

Here some entries with specific ObjectClass  cant be loaded with UserAccounts but same  can be loaded with Accounts . In my test script while using Accounts/Account to load the entries generated by dbgen i am not able to delete them.

But the entries which can be loaded by UserAccounts/UserAccount can be deleted . That means delete function is working with  UserAccounts/UserAccount but not working with Accounts/Account.

Comment 6 Simon Pichugin 2021-02-17 11:31:12 UTC

As per IRC discussion, the text should be changed to this:

.The `lib389` library no longer fails to delete entries discovered by the `Account` object

Previously, the `_protected` flag of the `Account` object in the `lib389` Directory Server library was enabled. As a consequence, `delete` operations failed. This update sets the flag to `False`. As a result, the library no longer fails if you delete or rename entries discovered by the `Account` object.

Thank you!

Comment 10 Akshay Adhikari 2021-03-29 13:02:48 UTC

Build tested: 389-ds-base-1.4.3.21-2.module+el8dsrv+10309+dd9f990e.x86_64
cockpit-389-ds-1.4.3.21-2.module+el8dsrv+10309+dd9f990e.noarch

============================================================================ test session starts ================================================================
platform linux -- Python 3.6.8, pytest-6.2.2, py-1.10.0, pluggy-0.13.1 -- /usr/bin/python3.6
cachedir: .pytest_cache
metadata: {'Python': '3.6.8', 'Platform': 'Linux-4.18.0-240.6.1.el8_3.x86_64-x86_64-with-redhat-8.3-Ootpa', 'Packages': {'pytest': '6.2.2', 'py': '1.10.0', 'pluggy': '0.13.1'}, 'Plugins': {'metadata': '1.11.0', 'html': '3.1.1'}}
389-ds-base: 1.4.3.21-2.module+el8dsrv+10309+dd9f990e
nss: 3.53.1-17.el8_3
nspr: 4.25.0-2.el8_2
openldap: 2.4.46-16.el8
cyrus-sasl: not installed
FIPS: disabled
rootdir: /root/389-ds-base/dirsrvtests, configfile: pytest.ini
plugins: metadata-1.11.0, html-3.1.1
collected 1 item                                                                                                                                                            

dirsrvtests/tests/suites/lib389/idm/account_test.py::test_account_delete PASSED                                                                                       [100%]

============================================================================ 1 passed in 11.53s =================================================================

Marking as VERIFIED.

Comment 12 errata-xmlrpc 2021-04-19 09:54:31 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 (Moderate: redhat-ds:11 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:1243