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 2119063 - entryuuid fixup tasks fails because entryUUID is not mutable
Summary: entryuuid fixup tasks fails because entryUUID is not mutable
Keywords:
Status: CLOSED ERRATA
Alias: None
Deadline: 2023-01-02
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: 389-ds-base
Version: 8.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.8
Assignee: Pierre Rogier
QA Contact: LDAP QA Team
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-17 12:29 UTC by thierry bordaz
Modified: 2023-05-16 09:42 UTC (History)
5 users (show)

Fixed In Version: 389-ds-1.4-8080020221115220516.6e2e7265
Doc Type: Bug Fix
Doc Text:
Cause: Rust plugin were setting the wrong flag for internal modify operation. Consequence: Entryuuid fixup task is broken on replicated instance. Fix: The flags have been fixed up Result: Entryuuid fixup task is now working on replicated instance
Clone Of:
Environment:
Last Closed: 2023-05-16 08:33:01 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 5158 0 None open entryuuid fixup tasks fails because entryUUID is not mutable 2022-08-17 12:31:07 UTC
Red Hat Issue Tracker IDMDS-2453 0 None None None 2022-08-17 12:34:32 UTC
Red Hat Issue Tracker IDMDS-2635 0 None None None 2022-11-15 20:25:54 UTC
Red Hat Issue Tracker RHELPLAN-131326 0 None None None 2022-08-17 12:34:36 UTC
Red Hat Product Errata RHBA-2023:2811 0 None None None 2023-05-16 08:33:34 UTC

Description thierry bordaz 2022-08-17 12:29:05 UTC 
Description of problem:
During entryuuid fixup task, if an entry is missing entryuuid fixup task fails to fix it

The goal of this BZ is to understand how differs the two reproducible testcases 


Version-Release number of selected component (if applicable):
Since 8.5 (entryuuid plugin)


How reproducible:
We have two tests that show opposite results although the look very similar.

It succeeds https://github.com/389ds/389-ds-base/issues/5158#issuecomment-1033903568
It fails https://github.com/389ds/389-ds-base/issues/5158#issuecomment-1035858853



Actual results:
CU claims fixup fails


Expected results:
fixup should succeeds
Comment 1 Pierre Rogier 2022-09-06 18:21:48 UTC 
The root cause is identified:
The different is that in one case replication is enabled and not in the other case.
And there is a real bug: The entryuuid fixup tasks fails on replicated environment
(The bug title is a bit misleading)
Comment 5 bsmejkal 2022-12-06 10:17:21 UTC 
============================================================================================================ test session starts =============================================================================================================
platform linux -- Python 3.6.8, pytest-7.0.1, pluggy-1.0.0 -- /usr/bin/python3.6
cachedir: .pytest_cache
metadata: {'Python': '3.6.8', 'Platform': 'Linux-4.18.0-440.el8.x86_64-x86_64-with-redhat-8.8-Ootpa', 'Packages': {'pytest': '7.0.1', 'py': '1.11.0', 'pluggy': '1.0.0'}, 'Plugins': {'metadata': '1.11.0', 'html': '3.2.0', 'libfaketime': '0.1.2', 'flaky': '3.7.0'}}
389-ds-base: 1.4.3.32-1.module+el8.8.0+17275+1a8f9618
nss: 3.79.0-10.el8_6
nspr: 4.34.0-3.el8_6
openldap: 2.4.46-18.el8
cyrus-sasl: 2.1.27-6.el8_5
FIPS: disabled
rootdir: /mnt/tests/rhds/tests/upstream/ds/dirsrvtests, configfile: pytest.ini
plugins: metadata-1.11.0, html-3.2.0, libfaketime-0.1.2, flaky-3.7.0
collected 2 items                                                                                                                                                                                                                            

dirsrvtests/tests/suites/entryuuid/replicated_test.py::test_entryuuid_with_replication PASSED                                                                                                                                          [ 50%]
dirsrvtests/tests/suites/entryuuid/replicated_test.py::test_entryuuid_fixup_with_replication PASSED                                                                                                                                    [100%]

======================================================================================================= 2 passed in 262.34s (0:04:22) ========================================================================================================
Comment 6 bsmejkal 2022-12-06 10:39:32 UTC 
As per comment #c5 marking as VERIFIED.
Comment 8 errata-xmlrpc 2023-05-16 08:33:01 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-2023:2811
Note You need to log in before you can comment on or make changes to this bug.