Replication agreements contain attributes which have invalid syntax

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/58

• Created at 2012-01-04 19:27:19 by mkosek
• Closed at 2019-08-23 22:16:58 as fixed
• Assigned to nobody
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=692211

---

https://bugzilla.redhat.com/show_bug.cgi?id=692211

Reported by Andrey Ivanov (andrey.ivanov@polytechnique.fr)

Description of problem:
However, i still have the syntax validation problem in cn=config for
replication agreements (have not tested with 1.2.8rcx but i think it has not
changed):

nsds5replicaChangesSentSinceStartup: value 0 invalid per syntax
nsds5replicaLastInitStart: value 0 invalid per syntax
nsds5replicaLastInitEnd: value 0 invalid per syntax

I think it's not the dn parsing problem, it is the schema definitions of
syntaxes for these attributes and the values that do not correspond to the
syntax :

(has integer syntax)nsds5replicaChangesSentSinceStartup: 1:11157/0 3:176/0
(has generalized time syntax)nsds5replicaLastInitStart: 0
(has generalized time syntax)nsds5replicaLastInitEnd: 0


attributeTypes: ( 2.16.840.1.113730.3.1.687 NAME
'nsds5replicaChangesSentSinceStartup' DESC 'Netscape defined attribute type'
EQUALITY integerMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SINGLE-VALUE
NO-USER-MODIFICATION X-ORIGIN 'Netscape Directory Server' )

attributeTypes: ( 2.16.840.1.113730.3.1.807 NAME 'nsds5replicaLastInitStart'
DESC 'Netscape defined attribute type' EQUALITY generalizedTimeMatch ORDERING
generalizedTimeOrderingMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 SINGLE-VALUE
NO-USER-MODIFICATION X-ORIGIN 'Netscape Directory Server' )

attributeTypes: ( 2.16.840.1.113730.3.1.808 NAME 'nsds5replicaLastInitEnd' DESC
'Netscape defined attribute type' EQUALITY generalizedTimeMatch ORDERING
generalizedTimeOrderingMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 SINGLE-VALUE
NO-USER-MODIFICATION X-ORIGIN 'Netscape Directory Server' )

Note: Separated from Bug 555577 - Syntax validation fails for "ou=NetscapeRoot"
tree

[389-ds-bot]

Comment from rmeggins (@richm) at 2012-01-10 06:14:48

batch move to milestone future

[389-ds-bot]

Comment from rmeggins (@richm) at 2012-08-14 19:57:05

set default ticket origin to Community

[389-ds-bot]

Comment from nkinder (@nkinder) at 2012-08-28 04:14:47

Added initial screened field value.

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2015-11-20 01:38:56

A good timing to fix this?

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2016-11-10 07:28:21

Per triage, set to FUTURE.

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2017-02-11 23:13:13

Metadata Update from @nhosoi:

• Issue set to the milestone: FUTURE

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2019-08-23 22:16:58

Metadata Update from @mreynolds389:

• Custom field reviewstatus adjusted to None (was: Needs Review)
• Issue close_status updated to: fixed
• Issue status updated to: Closed (was: Open)