#49946 upgrade of 389-ds-base could remove replication agreements.
Closed: wontfix 3 years ago Opened 3 years ago by mreynolds.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1623935

```text
Description of problem:

when a replication agreement starts with "cn=->...", the upgrade is removing
the entry.

I have checked upgrade from 1.3.6.1-26.el7_4 to 1.3.7.5-25.el7_5

I don't see yet what is removing the agremeent. It could be

setup-ds.pl -u

but I have not seen yet the root cause.

Still checking.

Version-Release number of selected component (if applicable):
389-ds-base-1.3.7.5-25.el7_5


Metadata Update from @mreynolds:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1623935

3 years ago

Metadata Update from @mreynolds:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 1.3.7.0 (was: 0.0 NEEDS_TRIAGE)

3 years ago

I have investigated this bug.

setup-ds.pl -u

is reading the entries in dse.ldif, normalizing dn's and rewriting the ldif file.

when trying to normalize a dn like "cn=->xxx,....", the Mozldap function:

my $ndn = normalizeDN($dn);

is returning NULL:

==========================
use Mozilla::LDAP::Conn;
use Mozilla::LDAP::Utils qw(normalizeDN);
use Mozilla::LDAP::LDIF;

$dn = "cn=->test,dc=parente,dc=local";

$ndn = normalizeDN($dn);

print("ndn is [$ndn]\n");

As a result, the entry cannot be re-added in dse.ldif

Should an attribute value starting by "->" be considered as valid ?

==========================

This diff is a potential fix:

diff --git a/ldap/admin/src/scripts/FileConn.pm b/ldap/admin/src/scripts/FileConn.pm
index dcea709..8a2a1af 100644
--- a/ldap/admin/src/scripts/FileConn.pm
+++ b/ldap/admin/src/scripts/FileConn.pm
@@ -360,7 +360,7 @@ sub add {
return $self->write();
}

  • if (exists($self->{$ndn})) {
  • if ($ndn && exists($self->{$ndn})) {
    $self->setErrorCode(LDAP_ALREADY_EXISTS);
    return 0;
    }
    [gparente@devel 389-ds-base]$

Metadata Update from @gparente:
- Issue assigned to gparente

3 years ago

Metadata Update from @gparente:
- Custom field reviewstatus adjusted to review (was: None)

3 years ago

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

3 years ago

b5e599a..c51748d 389-ds-base-1.3.9 -> 389-ds-base-1.3.9

Commit 26d7599 relates to this ticket

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/3005

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

a year ago

Login to comment on this ticket.

Metadata
Related Pull Requests