#51231 dsidm fails to delete an organizationalUnit entry.
Closed: wontfix 3 years ago by spichugi. Opened 3 years ago by mreynolds.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 8): Bug 1866294

Description of problem:
Trying to delete an organizationalUnit entry fails with this message:
Error: object of type 'Namespace' has no len()

Version-Release number of selected component (if applicable):
# cat /etc/redhat-release
Red Hat Enterprise Linux release 8.2 (Ootpa)
# rpm -qa | grep 389-ds-base
389-ds-base-1.4.2.12-2.module+el8dsrv+6428+6e54c518.x86_64
389-ds-base-libs-1.4.2.12-2.module+el8dsrv+6428+6e54c518.x86_64
#

How reproducible:
Always.

Steps to Reproduce:
1. Create the entry:
# dsidm -D "cn=Directory Manager" -b dc=example,dc=com ldap://localhost:389
organizationalunit create
Enter password for cn=Directory Manager on ldap://localhost:389:
Enter value for ou : toDelete
Successfully created toDelete
#

2. Get the entry details:
# dsidm -D "cn=Directory Manager" -b dc=example,dc=com ldap://localhost:389
organizationalunit get toDelete
Enter password for cn=Directory Manager on ldap://localhost:389:
dn: ou=toDelete,dc=example,dc=com
objectClass: top
objectClass: organizationalunit
ou: toDelete

#

3. Try to delete the entry:
# dsidm -D "cn=Directory Manager" -b dc=example,dc=com ldap://localhost:389
organizationalunit delete "ou=toDelete,dc=example,dc=com"
Enter password for cn=Directory Manager on ldap://localhost:389:
Error: object of type 'Namespace' has no len()
#
# dsidm -D "cn=Directory Manager" -b dc=example,dc=com ldap://localhost:389
organizationalunit delete ou=toDelete,dc=example,dc=com
Enter password for cn=Directory Manager on ldap://localhost:389:
Error: object of type 'Namespace' has no len()
#

Actual results:
The command fails.

Expected results:
The command should work.

Additional info:

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

3 years ago

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue priority set to: normal
- Issue set to the milestone: 1.4.2 (was: 0.0 NEEDS_TRIAGE)

3 years ago

Metadata Update from @spichugi:
- Issue assigned to spichugi

3 years ago

I can't reproduce it - the delete operation is successful.

Also, I've missed that bz1866294 is already assigned to @mreynolds, so I am leaving it for you, Mark, to proceed...

Metadata Update from @spichugi:
- Assignee reset

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

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