Comment 2 for bug 1970809

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

commit bdb6b40fe214a12731d19b2cf2b6a768e504b200
Author: Iago Estrela <email address hidden>
Date: Thu Apr 28 19:09:51 2022 -0300

    Fix runtime manifest triggered multiple times

    When max_cpu_frequency is set the API is triggering the
    ['platform::compute::config::runtime'] several times due to
    an additional RPC call to update_max_cpu_frequency in conductor.
    This commit fix this behavior by calling the conductor RPC
    method only if the host configure is not required, if is required
    the full manifest will be executed and there is no need to call
    update_max_cpu_frequency.

    Closes-Bug: 1970809

    Test plan:
    PASS: Bootstrap system and verify alarms.
    PASS: Host lock and unlock and verify alarms.

    Regression:
    PASS: Host-update max_cpu_frequency.
    PASS: Host-update max_cpu_frequency=max_cpu_default.

    Regression logs:
    https://paste.opendev.org/show/b1mRTZaNGS0bkAgpIsA5/

    Relates-To: https://storyboard.openstack.org/#!/story/2009886
    Task: 44882

    Signed-off-by: Iago Estrela <email address hidden>
    Change-Id: I2ff1c8e61a3189ea156cdeccda7c088620c80f41