Unable up version DM in upgraded subcloud

[Bo Yuan Chang]

Brief Description

In an upgraded DC subcloud Deployment management up versioning was not successful to image cloud-platform-deployment-manager. Central cloud was able to change DM version but subcloud was not successful it was trying to pull the older version.

severity

Major

Steps to Reproduce

1. DC system was upgraded from older version to newer version
2. Update DC central cloud and subcloud DM version was updated with cloud-platform-deployment-manager
3. Copy the DM ansible-playbook overrides file into working directory
4. Run: ansible-playbook /usr/local/share/applications/playbooks/wind-river-cloud-platform-deployment-manager.yaml -e “@dm-playbook-overrides.yaml”
5. Upload the files to dcmanager
6. Reconfigure the subclouds
dcmanager subcloud reconfig --sysadmin-password <password> --deploy-config deployment-config.yaml subcloud1
Verify subcloud DM version which is not updated as per description.

Actual Behavior

As the description subcloud DM version not updated.

Reproducibility

21.12

System Configuration

IPv6, DC system

Branch/Pull Time/Commit

From older version to 21.12

Timestamp/Logs

 kubelet, controller-0 Failed to pull image "registry.local:9001/docker.io/wind-river/cloud-platform-deployment-manager:WRCP_21.XX": rpc error: code = NotFound desc = failed to pull and unpack image "registry.local:9001/docker.io/wind-river/cloud-platform-deployment-manager:WRCP_21.XX": failed to resolve reference "registry.local:9001/docker.io/wind-river/cloud-platform-deployment-manager:WRCP_21.XX": registry.local:9001/docker.io/wind-river/cloud-platform-deployment-manager:WRCP_21.XX: not found

Test Activity

Pach testing

Workaround

removing /root/.ssh/know_hosts

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/ansible-playbooks/+/838949

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/starlingx/ansible-playbooks/+/838949
Committed: https://opendev.org/starlingx/ansible-playbooks/commit/0fb0898cd2cb5c601834d22fa6f1e5b0fb9a66c8
Submitter: "Zuul (22348)"
Branch: master

commit 0fb0898cd2cb5c601834d22fa6f1e5b0fb9a66c8
Author: BoYuan Chang <email address hidden>
Date: Thu Apr 21 15:24:54 2022 -0500

    Update SSH keys After Upgrade on Controller

    After subcloud upgrade, the system controller does not have the right
    subcloud ssh public key (the one that is backed up prior to upgrade)
    in its known_hosts. Hence, subcloud reconfiguration post upgrade fails
    due to invalid key. The solution is to update the system controller
    known_hosts after restoring subcloud ssh keys over subcloud upgrade.

    Test Plan:

    1. Upgrade in a DC lab and verify that there is no
       authentication failure
    2. Verify that subcloud upgrade is successful
    3. Verify that subcloud reconfigure post upgrade is successful

    Closes-Bug: 1969844
    Signed-off-by: BoYuan Chang <email address hidden>
    Change-Id: Ibd0b465648de234f8b2de42a4bee5c89c6c0e3d0