389-ds-base

#51051 Inconsistent user confirmation prompts
Closed: wontfix by mreynolds. Opened by mreynolds.

Closed: wontfix
Reopen Issue

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

Description of problem:
dsconf Instance sasl delete "SASL mapping name"  asking for confirmation: Type
'Yes I am sure' to continue:
1. [root@server-rhel8 ds]# dsconf localhost sasl list
anuj
Kerberos uid mapping
rfc 2829 dn syntax
rfc 2829 u syntax
uid mapping
2. [root@server-rhel8 ds]# dsconf localhost sasl delete anuj
Deleting SaslMapping cn=anuj,cn=mapping,cn=sasl,cn=config :
Type 'Yes I am sure' to continue: Yes I am sure
Successfully deleted cn=anuj,cn=mapping,cn=sasl,cn=config
Should it be something like "Yes" or "Y" or "y"
----------------------------------------------------
I also want to add the following example:
Removing instances:
[root@server-f29 ds]# dsctl slapd-server-f29 remove 
Not removing: if you are sure, add --do-it
[root@server-f29 ds]# dsctl slapd-server-f29 remove  --do-it 
About to remove instance (server-f29)!
If this is not what you want, press ctrl-c now ...
5 ...
4 ...
3 ...
2 ...
1 ...
Removing instance ...
Removed /etc/systemd/system/multi-user.target.wants/dirsrv@server-f29.service.
Completed instance removal
But with --remove-all there is no way to press ctrl-c, it just asks for one "Yes".
[root@server-f29 ds]# dsctl --remove-all
Are you sure you want to remove all the Directory Server instances?  Enter "Yes" to continue: Yes
Removing instance: slapd-localhost
Removed /etc/systemd/system/multi-user.target.wants/dirsrv@localhost.service.
All instances have been successfully removed
I'd argue that --remove-all is more disastrous than deleting just one instance. And we should be using countdown here as well. Or just here, but not when deleting one instance.

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

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

https://pagure.io/389-ds-base/pull-request/51053

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

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.3 (was: 0.0 NEEDS_TRIAGE)
- Issue tagged with: CLI

Commit 3def54d relates to this ticket

96184bc..60aa698 389-ds-base-1.4.3 -> 389-ds-base-1.4.3

ae2a2a4..ba3a704 389-ds-base-1.4.2 -> 389-ds-base-1.4.2

f3bd104..f261740 389-ds-base-1.4.1 -> 389-ds-base-1.4.1

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

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

CLI

None
None
None
None
None
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.