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:

The "start = False" option in dscreate is ignored.

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]
start = False
[slapd]
instance_name = default
[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 completes WITHOUT starting 389ds, as per docs, allowing further automated config to continue.

Additional info:

According to the docs in the generated template, if "start = False" is provided, the instance is (not) started.

# start (bool)
# Description: Starts the instance after the install completes. If false, the instance is created but started.
# Default value: True 
;start = True
start = False

It looks like the start function does not do anything.

This breaks automated installation of 389ds.

Running dscreate through strace, this shows that despite the "start = False" flag being present, not only is the server started, but subsequent calls inside dscreate are trying to connect to the server.

In this case the FQDN does not yet work, and thus the connection fails. When the FQDN does exist, it looks like the dscreate ignores the start flag and starts anyway.

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 ***

Just noticed this was closed as a duplicate of an unrelated bug, and was never fixed.

Cries in further automation pain.