This commit addresses the issue where the primary site's PGA status
remains 'in-sync' even after the secondary site becomes unreachable.
With this fix, the PGA status will be updated to 'unknown' upon the
secondary site's failure. Additionally, the status will transition to
'in-sync' once the secondary site is operational again.
If there are any changes in the association while the secondary site is
down, the PGA status will be set to failed. The sync status will
transition to "out-of-sync" upon secondary site recovery.
In this commit, the audit thread in the primary site will also update
PGA sync_status. If the primary site is down and the SPG is migrated to
secondary site, upon primary site recovery, its audit thread will update
the PGA sync_status on both sites accordingly.
Finally, the commit prevents the peergroup to from being updated in the
secondary site.
Test Case:
1. PASS - Shutdown of site2 (secondary site) results in the synchronization status of the peer group association transitioning from 'in-sync' to 'unknown'.
2. PASS - Restoration of site2 (secondary site) leads to the synchronization status of the peer group association on
the primary site changing to 'in-sync', and the peer
group association status on site2 also reflects 'in-sync'.
3. PASS - While secondary is is offline, execute some operations which
result in PGA sync_status being set to "failed". Recover secondary site and verify that the PGA sync_status is set to out-of-sync on both sites.
4. PASS - Verify that updating peer group on secondary site is disallowed.
5. PASS - Shut down the primary site, migrate the SPG to secondary site.
Restore the primary site while migration is in progress. Verify
that the PGA sync_status is out-of-sync. Verify that PGA sync_status is set to in-sync shortly after the migration is complete.
Reviewed: https:/ /review. opendev. org/c/starlingx /distcloud/ +/910150 /opendev. org/starlingx/ distcloud/ commit/ 26bb7011e4e51f5 b5ba728d08b214a 197a50d583
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 26bb7011e4e51f5 b5ba728d08b214a 197a50d583
Author: Zhang Rong(Jon) <email address hidden>
Date: Mon Feb 26 16:57:27 2024 +0800
Fix issues with PGA sync_status
This commit addresses the issue where the primary site's PGA status
remains 'in-sync' even after the secondary site becomes unreachable.
With this fix, the PGA status will be updated to 'unknown' upon the
secondary site's failure. Additionally, the status will transition to
'in-sync' once the secondary site is operational again.
If there are any changes in the association while the secondary site is
down, the PGA status will be set to failed. The sync status will
transition to "out-of-sync" upon secondary site recovery.
In this commit, the audit thread in the primary site will also update
PGA sync_status. If the primary site is down and the SPG is migrated to
secondary site, upon primary site recovery, its audit thread will update
the PGA sync_status on both sites accordingly.
Finally, the commit prevents the peergroup to from being updated in the
secondary site.
Test Case:
synchroniz ation status of the peer group association
transition ing from 'in-sync' to 'unknown'.
synchroniz ation status of the peer group association on
secondary site and verify that the PGA sync_status is set to
out- of-sync on both sites.
disallowed .
sync_ status is set to in-sync shortly after the migration is
complete.
1. PASS - Shutdown of site2 (secondary site) results in the
2. PASS - Restoration of site2 (secondary site) leads to the
the primary site changing to 'in-sync', and the peer
group association status on site2 also reflects 'in-sync'.
3. PASS - While secondary is is offline, execute some operations which
result in PGA sync_status being set to "failed". Recover
4. PASS - Verify that updating peer group on secondary site is
5. PASS - Shut down the primary site, migrate the SPG to secondary site.
Restore the primary site while migration is in progress. Verify
that the PGA sync_status is out-of-sync. Verify that PGA
Closes-Bug: 2055030
Change-Id: I67f42001186212 05c539b24eb764e 3cc5acf12c0
Signed-off-by: Zhang Rong(Jon) <email address hidden>