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

Bug 1816563

Summary:	Referential integrity scope values are not saved in cockpit
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, vashirov
Target Milestone:	DS11.1
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:40 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-24 09:45:32 UTC

Description of problem:
Referential integrity scope is not saved after 'Save config'. Associated fields values are removed.

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 'Plugins' tab
2. Enter a value in the 'Entry scope', 'Exclude entry scope' or 'container scope'
3. Press 'Save config'

Actual results:
A popup opens : 'Plugin referential integrity postoperation was successfully modified'
But the entered values are erased and fields are blank

Expected results:
Entered values are kept and displayed

Additional info:

Comment 3 sgouvern 2020-04-20 06:28:11 UTC

With builds : 
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

Referential integrity plugin values are now saved and displayed after 'save config' 

=> marking as verified

Comment 5 errata-xmlrpc 2020-04-29 08:04:40 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