Bug 1751128

Summary: Replication agreement disappears after browser refresh
Product: Red Hat Directory Server Reporter: bsmejkal
Component: cockpit-389-dsAssignee: mreynolds
Status: CLOSED ERRATA QA Contact: RHDS QE <ds-qe-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 11.0CC: afarley, lkrispen, mhonek, pasik, spichugi, tbordaz, vashirov
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: 389-ds-base- Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-06 12:42:36 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:

Description bsmejkal 2019-09-11 09:04:30 UTC
Description of problem:
When I create replication agreements and refresh browser (Firefox, Chrome), then the agreement disappears from WebUI and therefore can't be selected.

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

How reproducible:

Steps to Reproduce:
1. Create replication agreement
2. Refresh browser

Actual results:
After browser refresh, the agreement disappears. If I attempt to create new agreement with same attributes, WebUI shows error, that agreement already exists, but still won't show.

Expected results:
Created replication agreement should be present in WebUI.

Additional info:
The agreement exist in database and it shows in WebUI only if I create completely new agreement. After another refresh, both agreements disappear.

Comment 2 Viktor Ashirov 2019-10-29 21:36:21 UTC
Builds tested:

This issue is still reproducible, moving to ASSIGNED.

Comment 4 Viktor Ashirov 2019-11-04 14:25:14 UTC
Builds tested:

Replication agreement no longer disappears, marking as VERIFIED.

Comment 6 errata-xmlrpc 2019-11-06 12:42:36 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.