Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1751224

Summary: Cockpit : disabling a plugin after security port change will make the instance unable to restart
Product: Red Hat Directory Server Reporter: sgouvern
Component: cockpit-389-dsAssignee: mreynolds
Status: CLOSED CURRENTRELEASE QA Contact: RHDS QE <ds-qe-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 11.0CC: aadhikar, mreynolds, pasik, spichugi, tbordaz, vashirov
Target Milestone: ---   
Target Release: dirsrv-11.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sync-to-jira
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-26 15:36:41 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:
Attachments:
Description Flags
screenshot-1
none
screenshot-2
none
screenshot-3 none

Description sgouvern 2019-09-11 13:02:47 UTC 
Description of problem:

When restarting an instance having previously modified the security port, restarted, and then disabled a plugin, the instance won't start 
The same operation (disable the plugin, restart) performed on an instance on which the security port has not been changed doesn't prevent the instance to restart

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


How reproducible:


Steps to Reproduce:
1.Change the security port from 2636 to 636
2.Restart the instance
3.Go to Plugins, disable the 'fax syntax' plugin
4. Restart the instance 

-> Job for dirsrv failed because the control process exited with error code.
See "systemctl status dirsrv" and "journalctl -xe" for details.

Errors log :
[11/Sep/2019:08:38:57.526638304 -0400] - INFO - main - slapd stopped.
[11/Sep/2019:08:38:58.632342171 -0400] - ERR - dse_read_one_file - The entry cn=schema in file /usr/share/dirsrv/schema/06inetorgperson.ldif (lineno: 1) is invalid, error code 21 (Invalid syntax) - attribute type photo: Unknown attribute syntax OID "1.3.6.1.4.1.1466.115.121.1.23"
[11/Sep/2019:08:38:58.633479530 -0400] - ERR - setup_internal_backends - Please edit the file to correct the reported problems and then restart the server.

Systemctl status dirsrv output
Sep 11 08:38:58 ci-vm-10-0-132-195.hosted.upshift.rdu2.redhat.com systemd[1]: Starting 389 Directory Server inst2....
Sep 11 08:38:58 ci-vm-10-0-132-195.hosted.upshift.rdu2.redhat.com ns-slapd[17696]: [11/Sep/2019:08:38:58.632291843 -0400] - ERR - dse_read_one_file - The entry cn=schema in file /usr/share/dirsrv/schema/06i>
Sep 11 08:38:58 ci-vm-10-0-132-195.hosted.upshift.rdu2.redhat.com ns-slapd[17696]: [11/Sep/2019:08:38:58.633463162 -0400] - ERR - setup_internal_backends - Please edit the file to correct the reported probl>
Sep 11 08:38:58 ci-vm-10-0-132-195.hosted.upshift.rdu2.redhat.com systemd[1]: dirsrv: Main process exited, code=exited, status=1/FAILURE
Sep 11 08:38:58 ci-vm-10-0-132-195.hosted.upshift.rdu2.redhat.com systemd[1]: dirsrv: Failed with result 'exit-code'.
Sep 11 08:38:58 ci-vm-10-0-132-195.hosted.upshift.rdu2.redhat.com systemd[1]: Failed to start 389 Directory Server inst2..


Actual results:


Expected results:


Additional info:
Comment 1 mreynolds 2020-06-04 20:46:29 UTC 
So the UI bug here is that we do not report the error of the server failing to start properly, and the UI crashes.  Disabling plugins can have these kinds of effects on a server restart so I feel that behavior is expected, but the UI should handle the error gracefully.

Upstream ticket:

https://pagure.io/389-ds-base/issue/51136
Comment 4 Akshay Adhikari 2020-07-10 15:19:06 UTC 
Created attachment 1700616 [details]
screenshot-1

Build tested:

389-ds-base-1.4.2.12-3.module+el8dsrv+6923+6ab1d5c5.x86_64
cockpit-389-ds-1.4.2.12-3.module+el8dsrv+6923+6ab1d5c5.noarch

Steps:

1. Go to Plugins, disable the 'fax syntax' plugin
2. Restart the instance

The failure is still a silent one as only when I click on a different DS instance I see the error messages. I would expect these errors without clicking anywhere else (going on to any other instance or by clicking on any tab). I am updating the bug with screenshots of my finding. Let me know if this is not the expected way of testing this. 

Marking as ASSIGNED.
Comment 5 Akshay Adhikari 2020-07-10 15:21:07 UTC 
Created attachment 1700617 [details]
screenshot-2
Comment 6 Akshay Adhikari 2020-07-10 15:22:39 UTC 
Created attachment 1700618 [details]
screenshot-3
Comment 8 Simon Pichugin 2020-07-23 22:00:24 UTC 
The issue was fixed both in UI and lib389.
Comment 11 Akshay Adhikari 2020-09-24 12:51:15 UTC 
Build tested:

389-ds-base-1.4.3.11-1.module+el8dsrv+7557+bc264682.x86_64
cockpit-389-ds-1.4.3.11-1.module+el8dsrv+7557+bc264682.noarch

The UI is still not handling the error gracefully. Marking as ASSIGNED.
Comment 14 mreynolds 2021-07-26 15:36:41 UTC 
(In reply to thierry bordaz from comment #13)
> Mark do you know if this bug still exist after PF4 migration ?

Well it should be fixed now.  Sort of...  We no longer allow editing of most plugins.  So for this particular description of disabling the fax syntax, it is "resolved".