#50923 Add test - dsctl fails to remove instances with dashes in the name
Closed: wontfix 2 years ago by spichugi. Opened 2 years ago by spichugi.

Description of problem:
I have one instance installed:
slapd-host-10-0-137-3

I'm trying to remove the instance using dsctl, but it incorrectly tries to remove slapd-3 instead of slapd-host-10-0-137-3:

[root@server ~]# dsctl --remove-all
Are you sure you want to remove all the Directory Server instances? Enter "Yes" to continue: Yes
Removing instance: slapd-3
Instance configuration not found, no action will be taken
If you want us to cleanup anyway, recreate '/etc/dirsrv/slapd-3/dse.ldif'
All instances have been successfully removed

Version-Release number of selected component (if applicable):
389-ds-base-1.4.1.3-1.module+el8.1.0+3259+a5bc8ad3.x86_64

How reproducible:
always

Steps to Reproduce:
1. Create an instance with multiple dashes in the name
2. Try to remove all instances using dsctl --remove-all
3.

Actual results:
dsctl fails to remove the instance.

Expected results:
dsctl should remove the instance.


Metadata Update from @spichugi:
- Issue assigned to spichugi

2 years ago

Metadata Update from @spichugi:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

2 years ago

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

2 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/3976

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