Comment 7 for bug 1924786

Reviewed: https://review.opendev.org/c/starlingx/config/+/786972
Committed: https://opendev.org/starlingx/config/commit/47a03edc3bfe0ce41dbe6f2dd06e07214586415c
Submitter: "Zuul (22348)"
Branch: r/stx.4.0

commit 47a03edc3bfe0ce41dbe6f2dd06e07214586415c
Author: Angie Wang <email address hidden>
Date: Fri Apr 16 12:46:52 2021 -0400

    AIO-DX: Controller-1 fails to be unlocked after downgrade

    During stx4.0 to stx5.0 upgrade, controller-1 fails to be unlocked
    after downgrade due to the incorrect disk partition and physical
    volume information stored in stx4.0 DB that causes the puppet
    manifest apply failed during unlock.

    This is because cgts-vg size is decreased in stx5.0 and after
    controller-1 is upgraded to stx5.0, additional partition and pv
    are created at stx5.0 side to match the size in stx4.0. However,
    controller-0 is still running stx4.0 DB and it gets updated with
    the new created partition and pv info sent from controller-1 sysinv
    agent audit.

    This commit updates to ignore the disk partition and physical volume
    information sent back from a different version during upgrade.

    Tested:
    - AIO-DX upgrade from stx4.0 to stx5.0, verified upgrade is completed
    - controller-1 downgrade after it is upgraded and unlocked, verified
      upgrade abort is completed

    Change-Id: I5d7858e4b29d096437a5ddf94cd78c74fadfacad
    Closes-Bug: 1924786
    Signed-off-by: Angie Wang <email address hidden>
    (cherry picked from commit a24cd707a5cafaa2d49b25d1d5285c5c8582eb5d)