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 2065193 - Fixeup task does not fix entries with invalid uuid
Summary: Fixeup task does not fix entries with invalid uuid
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: 389-ds-base
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.7
Assignee: LDAP Maintainers
QA Contact: RHDS QE
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-17 13:23 UTC by sgouvern
Modified: 2022-11-08 10:30 UTC (History)
4 users (show)

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:
Clone Of:
Environment:
Last Closed: 2022-11-08 09:38:12 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 4877 0 None closed EntryUUID fixup to correct invalid entryuuids 2022-06-10 11:55:28 UTC
Red Hat Issue Tracker IDMDS-2109 0 None None None 2022-03-17 16:00:51 UTC
Red Hat Issue Tracker IDMDS-2265 0 None None None 2022-05-09 08:05:38 UTC
Red Hat Issue Tracker RHELPLAN-115894 0 None None None 2022-03-17 13:24:53 UTC
Red Hat Product Errata RHBA-2022:7552 0 None None None 2022-11-08 09:38:51 UTC

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


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