| Summary: | Non tombstone entry which dn starting with "nsuniqueid=...," cannot be deleted | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marcel Kolaja <mkolaja> |
| Component: | 389-ds-base | Assignee: | Noriko Hosoi <nhosoi> |
| Status: | CLOSED ERRATA | QA Contact: | Viktor Ashirov <vashirov> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.2 | CC: | gparente, mkolaja, msauton, nhosoi, nkinder, rmeggins, tscherf |
| Target Milestone: | rc | Keywords: | Regression, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 389-ds-base-1.3.5.10-13.el7_3 | Doc Type: | Bug Fix |
| Doc Text: |
Bug: Trying to delete a non tombstone entry fails when the generated tombstone is added to the cache.
Fix: Create a tombstone dn regardless of the rdn which starts with nsuniqueid or not.
Result: No more deleting entries fail.
|
Story Points: | --- |
| Clone Of: | 1390809 | Environment: | |
| Last Closed: | 2017-01-17 18:23:00 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 1390809 | ||
| Bug Blocks: | |||
|
Description
Marcel Kolaja
2016-12-06 15:34:07 UTC
========================================================== test session starts ========================================================== platform linux2 -- Python 2.7.5, pytest-3.0.5, py-1.4.32, pluggy-0.4.0 -- /usr/bin/python cachedir: .cache DS build: 1.3.5.10 B2017.04.1951 389-ds-base: 1.3.5.10-15.el7_3 nss: 3.21.0-17.el7 nspr: 4.11.0-1.el7_2 openldap: 2.4.40-13.el7 svrcore: 4.1.2-1.el7 rootdir: /mnt/tests/rhds/tests/upstream, inifile: plugins: html-1.13.0, cov-2.4.0, beakerlib-0.6 collected 1 items ticket48133_test.py::test_delete_dn_with_nsuniqueid PASSED ======================================================= 1 passed in 49.53 seconds ======================================================= Marking as VERIFIED 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, 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://rhn.redhat.com/errata/RHBA-2017-0088.html |