Bug 1816563 - Referential integrity scope values are not saved in cockpit
Summary: Referential integrity scope values are not saved in cockpit
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: cockpit-389-ds
Version: 11.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DS11.1
: dirsrv-11.1
Assignee: mreynolds
QA Contact: RHDS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-24 09:45 UTC by sgouvern
Modified: 2020-04-29 08:04 UTC (History)
4 users (show)

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:
Clone Of:
Environment:
Last Closed: 2020-04-29 08:04:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1961 0 None None None 2020-04-29 08:04:49 UTC

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


Note You need to log in before you can comment on or make changes to this bug.