Bug 1751123
Summary: | Cockpit : removing 'secure listen host' configuration value will make the instance fail to start | ||
---|---|---|---|
Product: | Red Hat Directory Server | Reporter: | sgouvern |
Component: | cockpit-389-ds | Assignee: | mreynolds |
Status: | CLOSED DUPLICATE | QA Contact: | RHDS QE <ds-qe-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 11.0 | CC: | lkrispen, mhonek, spichugi, tbordaz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-09-13 20:09:58 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
sgouvern
2019-09-11 08:49:07 UTC
Looking closer to the behavior, my points are : - it is misleading to see the 'secure listen host' field empty by default in cockpit, and then not to be able to come back to this empty state if you entered a value in this field by mistake for example. I understand that the nsslapd-securelistenhost parameter cannot be empty. In case of an empty value entered, if the parameter was removed from dse.ldif, it would induce a more logical behavior for the user - the same apply for 'Listen Host Address' in the server configuration settings - a misleading factor around this 'secure listen host' field is the imprecision in the description : it should be 'secure listen host Address', first for a clearer interpretation, and second to be consistent with the 'Listen Host Address' field in the server configuration settings - I noticed a discrepancy in the behaviors between 'secure listen host' and 'Listen Host Address' fields : if you perform the same steps for 'Listen Host Address' in the server configuration settings tab, you won't see any error "Invalid syntax - nsslapd-securelistenhost: value #0 invalid per syntax" when saving configuration. Instead, no message is displayed, and it's not clear weither the new configuration is taken into account or not. Both behaviors should be aligned This is being fully addressed in BZ#1751190 *** This bug has been marked as a duplicate of bug 1751190 *** |