When dscreate is used in the interactive mode, it suggests some default answers, like instance name and port numbers. But when these defaults were already used, dscreate has inconsistent suggestions. For example, I have one instance installed with the defaults:
dscreate
[root@server-f29 ds]# dscreate interactive Install Directory Server (interactive mode) =========================================== Enter system's hostname [server-f29.example.com]: Use strict hostname verification (set to "no" if using GSSAPI behind a load balancer) [yes]: Enter the instance name [server-f29]: Enter port number [389]: Create self-signed certificate database [yes]: Enter secure port number [636]: Enter Directory Manager DN [cn=Directory Manager]: Enter the Directory Manager password: Confirm the Directory Manager Password: Enter the database suffix (or enter "none" to skip) [dc=server-f29,dc=example,dc=com]: Create sample entries in the suffix [no]: Are you ready to install? [no]: yes
Now second time:
[root@server-f29 ds]# dscreate interactive Install Directory Server (interactive mode) =========================================== Enter system's hostname [server-f29.example.com]: Use strict hostname verification (set to "no" if using GSSAPI behind a load balancer) [yes]: Enter the instance name [server-f29]: server-f29-2 Enter port number []: 390 Create self-signed certificate database [yes]: Enter secure port number []: 637 Enter Directory Manager DN [cn=Directory Manager]: Enter the Directory Manager password: Confirm the Directory Manager Password: Enter the database suffix (or enter "none" to skip) [dc=server-f29,dc=example,dc=com]: Create sample entries in the suffix [no]: yes Are you ready to install? [no]: yes
The installer checks for port and if the default is already used, it doesn't suggest it, but for the instance name it doesn't do a similar check.
389-ds-base-1.4.0.19-20181127gita990d0440.fc29.x86_64
It would be good if the defaults came from the same source as the example-file code. The "idea" that I had (That I think wasn't done) was that interactive should just be creating the "file" and then we use the fromfile code.
Metadata Update from @firstyear: - 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
Using this ticket as a place holder for CLI/UI bugs found during the QE testing day:
https://pagure.io/389-ds-base/pull-request/50076
Metadata Update from @mreynolds: - Issue assigned to mreynolds
Metadata Update from @mreynolds: - Assignee reset - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Fix dsctl db2ldif
83223d5..a4632aa master -> master
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/3115
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.