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

Bug 2190454

Summary:	Newly created credentials or aliases in replication monitoring are not saved after page refresh
Product:	Red Hat Directory Server	Reporter:	Vladimir Cech <vcech>
Component:	cockpit-389-ds	Assignee:	LDAP Maintainers <idm-ds-dev-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	LDAP QA Team <idm-ds-qe-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	12.2	CC:	idm-ds-dev-bugs, mreynolds
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-04-28 14:36:09 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 Vladimir Cech 2023-04-28 13:10:30 UTC

Description of problem:
In Monitoring tab / Replication, when you refresh page after creating new Credential or Alias, the newly created Credentials or Aliases are not saved.

Version-Release number of selected component (if applicable):
389-ds-base-libs-2.2.7-2.module+el9dsrv+18726+78959e84.x86_64
389-ds-base-2.2.7-2.module+el9dsrv+18726+78959e84.x86_64
cockpit-389-ds-2.2.7-2.module+el9dsrv+18726+78959e84.noarch


How reproducible:
Always

Steps to Reproduce:
1. Enable replication, then click on Monitoring tab and click on replication in side menu.
2. Create new Credential or Alias.
3. Refresh page either with the button next to Replication Monitoring label or any  other way.
4. Newly created Aliases or Credentials are gone.

Actual results:
Newly created Aliases or Credentials are not saved.

Expected results:
Created Credentials or aliases are saved.


Additional info:

Comment 1 mreynolds 2023-04-28 14:36:09 UTC

This is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2030884

*** This bug has been marked as a duplicate of bug 2030884 ***