After updating the subcloud and running the PGA sync command the data is not getting sync in the secondary site

[Jon Zhang]

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:bf60:1102::2-fdff:719a:bf60:1102::10 --floating-address fdff:719a:bf60:1102::2 --controller0-address fdff:719a:bf60:1102::3 --gateway-address fdff:719a:bf60:1102::1 admin fdff:719a:bf60:1102:: 64
system network-add admin admin true $(system addrpool-list | grep admin | awk '{print $2}')
system interface-network-assign controller-0 admin0 admin
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-install-values.yaml --bootstrap-address 2620:10a:a001:d41::143 --management-subnet fdff:719a:bf60:1102::/64 --management-gateway-ip fdff:719a:bf60:1102::1 --management-start-ip fdff:719a:bf60:1102::2 --management-end-ip fdff:719a:bf60:1102::10
dcmanager subcloud manage subcloud3
dcmanager peer-group-association sync 1
On Primary site:

[sysadmin@controller-0 ~(keystone_admin)]$ dcmanager subcloud show subcloud3 | grep -E 'management_subnet|management_start_ip|management_end_ip|management_gateway_ip|deploy_status'

 deploy_status complete
 management_subnet fdff:719a:bf60:1102::/64
 management_start_ip fdff:719a:bf60:1102::2
 management_end_ip fdff:719a:bf60:1102::10
 management_gateway_ip fdff:719a:bf60:1102::1
[sysadmin@controller-0 ~(keystone_admin)]$

On the Secondary site:

[sysadmin@controller-0 ~(keystone_admin)]$ dcmanager subcloud show subcloud3 | grep -E 'management_subnet|management_start_ip|management_end_ip|management_gateway_ip|deploy_status'

 deploy_status secondary
 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
[sysadmin@controller-0 ~(keystone_admin)]$

Note: Any update on the below parameters should be sync in secondary site.

[sysadmin@controller-0 ~(keystone_admin)]$ dcmanager subcloud update
usage: dcmanager subcloud update [-h] [-f \{json,shell,table,value,yaml}] [--name NAME] [--description DESCRIPTION]
                                 [--location LOCATION] [--group GROUP] [--management-subnet MANAGEMENT_SUBNET]
                                 [--management-gateway-ip MANAGEMENT_GATEWAY_IP] [--management-start-ip MANAGEMENT_START_IP]
                                 [--management-end-ip MANAGEMENT_END_IP] [--sysadmin-password SYSADMIN_PASSWORD]
                                 [--bootstrap-address BOOTSTRAP_ADDRESS] [--install-values INSTALL_VALUES] [--bmc-password BMC_PASSWORD]
                                 [--bootstrap-values BOOTSTRAP_VALUES] [--peer-group PEER_GROUP]
                                 subcloud

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:a001:d41::1080

Secondary site - 2620:10a:a001:d41::1180

Load info (eg: 2022-03-10_20-00-07)

Last Pass

Timestamp/Logs

Alarms

Test Activity

Feature Testing

Workaround

Describe workaround if available

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/distcloud/+/912514

[OpenStack Infra (hudson-openstack)]

Change abandoned by "Jon Zhang <email address hidden>" on branch: master
Review: https://review.opendev.org/c/starlingx/distcloud/+/912514
Reason: abandon