After updating the subcloud and running the PGA sync command the data is not getting sync in the secondary site
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
In Progress
|
Undecided
|
Unassigned |
Bug Description
Brief Description
After updating the subcloud and running the PGA sync command the data is not getting sync in the secondary site
Severity
Major
Steps to Reproduce
1) Create the protection group from the siteA (primary) to siteB(secondary)
Add the admin n/w or interface in the subcloud (subcloud3)
system host-lock controller-0
system host-if-add -V 496 -c platform controller-0 admin0 vlan sriov0
system host-lock controller-0
system addrpool-add --ranges fdff:719a:
system network-add admin admin true $(system addrpool-list | grep admin | awk '{print $2}')
system interface-
Wait for alarm to get clear from the subcloud -> fm alarm-list
dcmanager subcloud unmanage subcloud3
dcmanager subcloud update subcloud3 --sysadmin-password Li69nux* --bmc-password Li69nux* --install-values subcloud3-
dcmanager subcloud manage subcloud3
dcmanager peer-group-
On Primary site:
[sysadmin@
deploy_status complete
management_subnet fdff:719a:
management_
management_end_ip fdff:719a:
management_
[sysadmin@
On the Secondary site:
[sysadmin@
deploy_status secondary
management_subnet fdff:719a:
management_
management_end_ip fdff:719a:
management_
[sysadmin@
Note: Any update on the below parameters should be sync in secondary site.
[sysadmin@
usage: dcmanager subcloud update [-h] [-f \{json,
Expected Behavior
After subcloud update data should be sync in the secondary site
Actual Behavior
After subcloud update data is not getting sync in the secondary site
Reproducibility
Yes
System Configuration
Primary site - 2620:10a:
Secondary site - 2620:10a:
Load info (eg: 2022-03-
Last Pass
Timestamp/Logs
Alarms
Test Activity
Feature Testing
Workaround
Describe workaround if available
Fix proposed to branch: master /review. opendev. org/c/starlingx /distcloud/ +/912514
Review: https:/