Bug 2065193

Summary:	Fixeup task does not fix entries with invalid uuid
Product:	Red Hat Enterprise Linux 8	Reporter:	sgouvern
Component:	389-ds-base	Assignee:	LDAP Maintainers <ldap-maint>
Status:	CLOSED ERRATA	QA Contact:	RHDS QE <ds-qe-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.6	CC:	gkimetto, ldap-maint, mreynolds, tbordaz
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.7	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	sync-to-jira
Fixed In Version:	389-ds-base-1.4.3.30-3.module+el8.7.0+15600+347cafc6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-08 09:38:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description sgouvern 2022-03-17 13:23:40 UTC

Description of problem:
fixup task does not fix entries with invalid uuid, as it skips entries already having 'entryuuid' attribute

Version-Release number of selected component (if applicable):
389-ds-base 1.4.3.18-6 

How reproducible:
always

Steps to Reproduce:
run suites/entryuuid/basic_test.py::test_entryuuid_import_and_fixup_of_invalid_values

Actual results:

Entries with invalid uuid are not fixed up

Test fails with 
AssertionError: assert 'INVALID_UUID' != 'INVALID_UUID' 

Expected results:
The entries with invalid uuid should be fixed by fixeup task
The test should pass

Additional info:
Problem is that entryuuid plugin fixup task get broken by 0016-Issue-4775-Add-entryuuid-CLI-and-Fixup-4776.patch
see https://issues.redhat.com/browse/IDMDS-1997

Comment 5 thierry bordaz 2022-06-10 11:55:28 UTC

Fixed in 389-ds-base-1.4.3.30-3.module+el8.7.0+15600+347cafc6 => MODIFIED

Comment 10 errata-xmlrpc 2022-11-08 09:38:12 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 (389-ds:1.4 bug fix and enhancement 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/RHBA-2022:7552