Description of problem:

Customer wants to know why after every restart of rhds all of their suffixes come to "Not Initialized" state even though the replication is working properly.

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

Red Hat Enterprise Linux release 8.7 (Ootpa)

389-ds-base-1.4.3.31-11.module+el8dsrv+17815+4f95348d.x86_64 Tue Mar 7 14:55:37 2023
389-ds-base-libs-1.4.3.31-11.module+el8dsrv+17815+4f95348d.x86_64 Tue Mar 7 14:55:36 2023
kernel-4.18.0-372.13.1.el8_6.x86_64 Mon Jul 11 10:59:49 2022

Steps to Reproduce:
1. In a multi-master replication environment, open the console cockpit.
2. Open Red Hat Directory Server.
3. Go to Replication > Agreements.
4. Check the status as initialized
5. Restart the rhds instal, clicking in 'Actions' restart.
6. Again, Go to Replication > Agreements.
7. Check the status now says that is "Not Initilized"

Actual results:

After rhds restart all suffixes go to "Not Initialized" status.

Expected results:

Show the initialized status, since the first initialization was executed properly.

Additional info:

My local environment:

[root@rhds1 ~]# dsconf rhds1 replication status --suffix=dc=example,dc=net

{ "agmt-name":[ "rhds1-to-rhds2" ], "replica":[ "rhds2.lab.example.net:636" ], "replica-enabled":[ "on" ], "update-in-progress":[ "FALSE" ], "last-update-start":[ "19700101000000Z" ], "last-update-end":[ "19700101000000Z" ], "number-changes-sent":[ "0" ], "number-changes-skipped":[ "unavailable" ], "last-update-status":[ "Error (0) No replication sessions started since server startup" ], "last-init-start":[ "20230417203423Z" ], "last-init-end":[ "20230417203425Z" ], "last-init-status":[ "Error (0) Total update succeeded" ], "reap-active":[ "0" ], "replication-status":[ "Not in Synchronization: supplier (643da385000000010000) consumer (Unavailable) State (green) Reason (error (0) no replication sessions started since server startup)" ], "replication-lag-time":[ "unavailable" ] } [root@rhds1 ~]# dsctl rhds1 restart Instance "rhds1" has been restarted [root@rhds1 ~]# dsconf rhds1 replication status --suffix=dc=example,dc=net {'agmt-name': ['rhds1-to-rhds2'], 'replica': ['rhds2.lab.example.net:636'], 'replica-enabled': ['on'], 'update-in-progress': ['FALSE'], 'last-update-start': ['19700101000000Z'], 'last-update-end': ['19700101000000Z'], 'number-changes-sent': ['0'], 'number-changes-skipped': ['unavailable'], 'last-update-status': ['Error (0) No replication sessions started since server startup'], 'last-init-start': ['19700101000000Z'], 'last-init-end': ['19700101000000Z'], 'last-init-status': ['unavailable'], 'reap-active': ['0'], 'replication-status': ['Not in Synchronization: supplier (643da385000000010000) consumer (Unavailable) State (green) Reason (error (0) no replication sessions started since server startup)'], 'replication-lag-time': ['unavailable']}

[root@rhds1 ~]#

[root@rhds1 ~]# dsconf rhds1 replication status --suffix=dc=example,dc=net
{
"agmt-name":[
"rhds1-to-rhds2"
],
"replica":[
"rhds2.lab.example.net:636"
],
"replica-enabled":[
"on"
],
"update-in-progress":[
"FALSE"
],
"last-update-start":[
"19700101000000Z"
],
"last-update-end":[
"19700101000000Z"
],
"number-changes-sent":[
"0"
],
"number-changes-skipped":[
"unavailable"
],
"last-update-status":[
"Error (0) No replication sessions started since server startup"
],
"last-init-start":[
"19700101000000Z"
],
"last-init-end":[
"19700101000000Z"
],
"last-init-status":[
"unavailable"
],
"reap-active":[
"0"
],
"replication-status":[
"Not in Synchronization: supplier (643da385000000010000) consumer (Unavailable) State (green) Reason (error (0) no replication sessions started since server startup)"
],
"replication-lag-time":[
"unavailable"
]
}