#354 Recover original configuration of modified attributeType on schema
Closed: wontfix 3 years ago by spichugi. Opened 11 years ago by mbarper.

1.- I have apply the syntax modification for nsViewFilter like this:

$ ldapmodify -H ldaps://hostxxxx -D "cn=Directory Manager" -x -W << EOF << EOF
dn: cn=schema
changetype: modify
add: attributeTypes
attributeTypes: ( 2.16.840.1.113730.3.1.3023 NAME 'nsViewFilter' DESC 'Netscape defined attribute type' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 X-ORIGIN 'Netscape Directory Server' )
-
EOF

2.- I want to revert this change, that is, I wan to use the syntax in the 02common.ldif (the original) for this attribute, and erase the entry in 99user.ldif for this attribute. I can delete it because of the MAY clause in objectClasses. I can't stop the DS and remove the line in the schema file because of schema replication. Can I perform this??? How???

I need to know how to do this (if possible) due to conflicts with some application or error which could appear.

The command to erase the attributeType fails like this:

$ ldapmodify -H ldaps://hostxxxx -D "cn=Directory Manager" -x -W << EOF
dn: cn=schema
changetype: modify
delete: attributeTypes
attributeTypes: ( 2.16.840.1.113730.3.1.3023 NAME 'nsViewFilter' DESC 'Netscape defined attribute type' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 X-ORIGIN 'Netscape Directory Server' )
-
EOF
Enter LDAP Password:
modifying entry "cn=schema"
ldap_modify: Server is unwilling to perform (53)
additional info: attribute type nsviewfilter: Is included in the MAY list for object class nsView. Cannot delete.

It's related with https://fedorahosted.org/389/ticket/349

http://lists.fedoraproject.org/pipermail/389-users/2012-April/014533.html


set default ticket origin to Community

Added initial screened field value.

Metadata Update from @nkinder:
- Issue assigned to rmeggins
- Issue set to the milestone: FUTURE

7 years ago

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: None
- Issue tagged with: Schema

3 years ago

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.4 (was: FUTURE)

3 years ago

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/354

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
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata