RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Installation a 389ds server bound to localhost is not possible.

Version-Release number of selected component (if applicable):

389-ds-base-1.4.2.4-8.module_el8.2.0+366+71e3276f.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Create slapd-default.inf as follows:

[general]
full_machine_name = localhost
[slapd]
instance_name = default
self_sign_cert = False
[backend-userroot]

2. Run "dscreate from-file slapd-default.inf"
3.

Actual results:

+ /usr/sbin/dscreate from-file /etc/dirsrv/slapd-default.inf
Starting installation...
Error: Can't contact LDAP server - 107 - Transport endpoint is not connected

Expected results:

Installation successful, allowing further automated config to continue.

Additional info:

Error handling appears to be missing in the dscreate tool. Telling me that it can't contact the LDAP server is meaningless, why was it trying to connect to the LDAP server, and might that tell me what is wrong.

Looking at the machine after dscreate fails.

Slapd is running as expected, bound only to port 389, as expected:

ns-slapd 16350 dirsrv    8u  IPv6             133377      0t0       TCP *:ldap (LISTEN)

It looks like the dscreate tool doesn't pay attention to the self_sign_cert flag, and always tries to contact the server on the secure port.

In addition, the dscreate tool binds to all interfaces, and not just localhost.

Pulling this apart with strace, while the dscreate has been asked to connect to localhost.localdomain, the dscreate tool is trying to connect to the FQDN of the machine, which in this case does not (yet) work.

The real fix for dscreate seems to be for the server to bind to a unix domain docket, and then use the unix domain socket for all setup communication. This means the server is not exposed externally in a half configured or insecure state.

This is important for automation - other machines that might also be automatically created will want to connect to 389ds, and this must only succeed when 389ds is 100% configured. Prior to this, everything outside the box must see "connection refused".

Closing as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1872930

*** This bug has been marked as a duplicate of bug 1872930 ***