Comment 1 for bug 2002258

Reviewed: https://review.opendev.org/c/starlingx/config/+/869535
Committed: https://opendev.org/starlingx/config/commit/a5cf7d2b45c71d35483d356d9a552f7b580cebda
Submitter: "Zuul (22348)"
Branch: master

commit a5cf7d2b45c71d35483d356d9a552f7b580cebda
Author: Girish Subramanya <email address hidden>
Date: Sun Jan 8 20:50:00 2023 -0500

    Alarm 250.001 persists after first install on sub-cloud

    After system controller and subcloud install success, one DX subcloud
    witnessed a 250.001 alarm; the alarm was seen on one of 10 sub-clouds

    The Alarm that persisted is for Config UUID with reload-required set
    The Alarm was seen on the Standby Subcloud controller on a DX subcloud

    Performing comparison of configured manifest post restart with target
    The clear of the reboot_required config_target is based on the First
    Report from sysinv-agent occuring within a limited time after restart

    Test Plan:
    Verify SX Subcloud Install is successful and no 250.001 alarm exists
    Verify DX Subcloud Install is successful and no 250.001 alarm exists
    Verify for reboot required config eg. ‘system ntp-modify’,
      Alarm persists till next lock/unlock sequence

    Regression:
    Verify AIO-SX, AIO-DX Install is successful
    Verify Distributed Clod Controller and Sub-cloud install is successful
    Verify for reboot required config eg. ‘system ntp-modify’,
      Alarm persists till next lock/unlock sequence

    Closes-Bug: 2002258

    Signed-off-by: Girish Subramanya <email address hidden>
    Change-Id: I95f0642c97367a3925cd009f6be8bb1c140a210f