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

Bug 1817415

Summary:	The 'Security Settings' refresh button does not work
Product:	Red Hat Directory Server	Reporter:	sgouvern
Component:	cockpit-389-ds	Assignee:	mreynolds
Status:	CLOSED ERRATA	QA Contact:	RHDS QE <ds-qe-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	11.0	CC:	lkrispen, spichugi, tbordaz
Target Milestone:	---
Target Release:	dirsrv-11.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.4.2.11-1.module+el8dsrv+6254+69a018e7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-29 08:04: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:

Description sgouvern 2020-03-26 10:15:19 UTC

Description of problem:
On the 'Server Settings'/'Security' tab, the 'refresh configuration settings' button has no effect

Version-Release number of selected component (if applicable):
cockpit-389-ds-1.4.2.9-1.module+el8dsrv+6001+1cbc6dcf.noarch

How reproducible:
always

Steps to Reproduce:
1. Go to 'Server Settings'/'Security' tab
2. Do a change in 'Security configuration' 
3. restart or not the instance
4. click on 'Security Settings' refresh button

Actual results:
Nothing happens

Expected results:
A 'action in progress' circle is displayed, as on other windows.
Configuration is actually refreshed

Additional info:

Comment 3 sgouvern 2020-04-17 12:57:37 UTC

With cockpit-389-ds-1.4.2.12-1.module+el8dsrv+6328+f04d7471.noarch / 389-ds-base-1.4.2.12-1.module+el8dsrv+6328+f04d7471.x86_64

The refresh button now works correctly on 'Server Settings'/'Security' tab / 'Security configuration' 

=> marking as verified

Comment 5 errata-xmlrpc 2020-04-29 08:04:41 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1961