Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some replication status data are reset upon a restart #6470

Open
tbordaz opened this issue Jan 3, 2025 · 0 comments · May be fixed by #6471
Open

Some replication status data are reset upon a restart #6470

tbordaz opened this issue Jan 3, 2025 · 0 comments · May be fixed by #6471
Labels
needs triage The issue will be triaged during scrum

Comments

@tbordaz
Copy link
Contributor

tbordaz commented Jan 3, 2025

Issue Description
The replication agreement contains operational attributes related to the total init

  • nsds5replicaLastInitStart
  • nsds5replicaLastInitEnd
  • nsds5replicaLastInitStatus

Those attributes are reset after restarting DS. So the consumer may erroneously appear not yet initialized and
we are loosing the time when it was initialized.

Package Version and Platform:

  • all versions

Steps to Reproduce
testcase provided

Expected results
The total init date (start/end) and the total init status should be preserved during restart

@tbordaz tbordaz added the needs triage The issue will be triaged during scrum label Jan 3, 2025
tbordaz added a commit to tbordaz/389-ds-base that referenced this issue Jan 3, 2025
Bug description:
	The replication agreement contains operational attributes
	related to the total init: nsds5replicaLastInitStart,
	nsds5replicaLastInitEnd, nsds5replicaLastInitStatus.
	Those attributes are reset at restart

Fix description:
	When reading the replication agreement from config
	(agmt_new_from_entry) restore the attributes into
	the in-memory RA.
	Updates the RA config entry from the in-memory RA
	during shutdown/cleanallruv/enable_ra

fixes: 389ds#6470

Reviewed by:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage The issue will be triaged during scrum
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant