Comment 7 for bug 1851874

Reviewed: https://review.opendev.org/696030
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=238b196d3a9d244ce6e86f0fc7a2d14c2b3878d7
Submitter: Zuul
Branch: master

commit 238b196d3a9d244ce6e86f0fc7a2d14c2b3878d7
Author: Sun Austin <email address hidden>
Date: Thu Nov 21 21:23:00 2019 +0800

    Additional condition is comparison when doing config check out of date

    This will fix below scenario:
    Controller-0 is installed and some configs were applied. Config
    f5d83753-c485-4221-b4aa-e986f5421d6d is the target config and requests
    boot.
    After controller-0 is unlocked and reboot.another request with uuid
    29c89b7e-51fe-40cb-8700-e22c83ed5fa9 is coming,then the config_target is
    set to a9c89b7e-51fe-40cb-8700-e22c83ed5fa9;
    Once 29c89b7e-51fe-40cb-8700-e22c83ed5fa9 was applied,the config should
    be cleared, but because 29c89b7e-51fe-40cb-8700-e22c83ed5fa9 is not same
    as a9c89b7e-51fe-40cb-8700-e22c83ed5fa9,the alarm can not be cleared.

    In this fix, tracking list for reboot config and clear it once config is
    applied. the out of date config will be clear if reboot config tracking
    is empty and config_applied w/ reboot config flag is equal config_target

    Closes-Bug: 1851874
    Change-Id: Iabeab338bc3fb4615cefcff9e4ae9402e4216321
    Signed-off-by: Sun Austin <email address hidden>