Comment 0 for bug 2054123

Brief Description
-----------------
SPG is not changing 'sync_status' from 'in-sync' to 'out-of-sync' after running any of the following operations:

After creating peer association and re-installing the peer, i.e., sync both sites and then re-install secondary site.
Adding subcloud(s) to the SPG.
Removing subcloud(s) from the SPG.
Updating subcloud(s) in the SPG.

Severity
--------
Major

Steps to Reproduce
------------------
1. Create the system peer group from Site A to Site B
2. Create System peer from Site B to Site A
3. Create the subcloud peer group in the Site A
4. Add subcloud(s) to the peer group
5. Create peer group association to associate system peer and subcloud peer group - Site A
6. Check current sync status on Sites A and B. Verify they are 'in-sync'
dcmanager peer-group-association list
7. Now, remove the subcloud from the SPG (please also test adding and updating)
Note: Does not sync it manually.
8. After more than an hour, verify the status is still 'in-sync'

Expected Behavior
------------------
'sync_status' should be 'out-of-sync' after making changes in a subcloud that is part of the SPG.

Actual Behavior
----------------
'sync_status' 'in-sync'

Reproducibility
---------------
100% reproducible

System Configuration
--------------------
Distributed Cloud

Branch/Pull Time/Commit
-----------------------
22.12 MR3 iteration 11

Last Pass
---------
New test scenario

Timestamp/Logs
--------------
// Subcloud 3 and 4 in the SPG

$ dcmanager subcloud-peer-group list-subclouds 1 --------+----------+---------------+----------------------------+----------------------------+---------------+-----------------+
| 11 | subcloud4 | None | None | 22.12 | managed | online | complete | fdff:719a:bf60:1109::/64 | fdff:719a:bf60:1109::2 | fdff:719a:bf60:1109::ffff | fdff:719a:bf60:1109::1 | fdff:719a:bf60:1096: :1 | 1 | 1 | 2024-02-02 21:58:33.703653 | 2024-02-06 20:17:32.238938 | None | None |
| 12 | subcloud3 | None | None | 22.12 | managed | online | complete | fdff:719a:bf60:1099::/64 | fdff:719a:bf60:1099::2 | fdff:719a:bf60:1099::ffff | fdff:719a:bf60:1099::1 | fdff:719a:bf60:1096: :1 | 1 | 1 | 2024-02-07 11:10:44.657089 | 2024-02-07 13:15:26.553700 | None | None |
+----+-----------+-------------+----------+------------------+------------+--------------+---------------+--------------------------+------------------------+---------------------------+------------------------+---------------------
 // subcloud3 removed from the SPG

$ dcmanager subcloud update subcloud3 --peer-group none
+-----------------------------+----------------------------+
| Field | Value |
+-----------------------------+----------------------------+
| id | 12 |
| name | subcloud3 |
| description | None |
| location | None |
| software_version | 22.12 |
| management | managed |
| availability | online |
| deploy_status | complete |
| management_subnet | fdff:719a:bf60:1099::/64 |
| management_start_ip | fdff:719a:bf60:1099::2 |
| management_end_ip | fdff:719a:bf60:1099::ffff |
| management_gateway_ip | fdff:719a:bf60:1099::1 |
| systemcontroller_gateway_ip | fdff:719a:bf60:1096::1 |
| group_id | 1 |
| peer_group_id | None |
| created_at | 2024-02-07T11:10:44.657089 |
| updated_at | 2024-02-08T11:27:08.919357 |
| backup_status | None |
| backup_datetime | None |
+-----------------------------+----------------------------+
// Still showing as 'in-sync' on both sites.

$ dcmanager peer-group-association list
+----+---------------+----------------+---------+-------------+---------------------+
| id | peer_group_id | system_peer_id | type | sync_status | peer_group_priority |
+----+---------------+----------------+---------+-------------+---------------------+
| 1 | 1 | 1 | primary | in-sync | 1 |
+----+---------------+----------------+---------+-------------+---------------------+

Test Activity
-------------
Feature Testing

Workaround
----------
None