389-ds-base

#49320 Activating roles returns error 16
Closed: wontfix Opened by mreynolds.

Closed: wontfix
Reopen Issue

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

Description of problem: When activating a role, it returns error 16 and it
doesn't print if role is active or not.
Version-Release number of selected component (if applicable):
389-ds-base-1.3.6.1-16
How reproducible: Consistently
Steps to Reproduce:
1. Install 389-ds-base-1.3.6.1-16
2. Create instance and add few user entries.
3. Add a role.
[root@cloud-qe-06 389ds-replica]# ldapmodify -ax -p 13905 -h localhost -D
"cn=Directory Manager" -w Secret123 << EOF
dn: cn=nrole1,dc=example,dc=com
objectclass: LDAPsubentry
objectclass: nsRoleDefinition
objectclass: nsComplexRoleDefinition
objectclass: nsNestedRoleDefinition
nsRoleDN: uid=usr4role9,dc=example,dc=com
> EOF
adding new entry "cn=nrole1,dc=example,dc=com"
4. Try ns-inactivate.pl and ns-inactivate.pl scripts in sequence.
[root@cloud-qe-06 389ds-replica]# ns-accountstatus.pl -Z slapd-deftestinst -p
13905 -h localhost -D "cn=Directory Manager" -w Secret123 -I
cn=nrole1,dc=example,dc=com
cn=nrole1,dc=example,dc=com - inactivated (directly locked).
[root@cloud-qe-06 389ds-replica]# ns-activate.pl -Z slapd-deftestinst -p 13905
-h localhost -D "cn=Directory Manager" -w Secret123 -I
cn=nrole1,dc=example,dc=com
cn=nrole1,dc=example,dc=com activated.
[root@cloud-qe-06 389ds-replica]# ns-activate.pl -Z slapd-deftestinst -p 13905
-h localhost -D "cn=Directory Manager" -w Secret123 -I
cn=nrole1,dc=example,dc=com
ldap_modify: No such attribute (16)
ns-activate.pl script returns error 16 for roles which are active.
Actual results: It returns error 16.
Expected results:  Its expected to return error 100, if its already active or
activated.

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

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

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 backlog (was: 0.0 NEEDS_TRIAGE)

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

0001-Ticket-49320-Activating-already-active-role-returns-.patch

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

Metadata Update from @firstyear:
- Custom field reviewstatus adjusted to ack (was: review)

0953e60..4060848 master -> master

703be0e..adc6a8b 389-ds-base-1.3.7 -> 389-ds-base-1.3.7

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

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

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)
Metadata
None
None
None
None
None
ack
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.