sysinv allows k8s upgrade to start with platform memory alarm, but doesn't allow kubelet upgrade

[Boovan Rajendran]

Brief Description:

When using the "-f" option we can start a K8s upgrade when there is a platform memory alarm, but sysinv will not attempt a kubelet upgrade when there is a platform memory alarm, even with the "-f" option.

Severity:

Minor

Steps to Reproduce:

Attempt a kubelet upgrade on a host with a platform memory alarm.

Expected Behavior:

"-f" option allows it to continue, like it does for the initial command to begin the K8s upgrade.

Actual Behavior:

sysinv rejects the kubelet upgrade command due to the memory alarm.

Reproducibility:

Reproducible

System Configuration:

All

Last Pass:

Not known

Timestamp/Logs:

Alarms:

platform memory alarm

Test Activity:

developer testing

Workaround:

bump up platform memory to get rid of alarm.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/config/+/867982

[OpenStack Infra (hudson-openstack)]

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

commit f0eb77e52e1d0d4e7317879b1f71353af6c4f05d
Author: Boovan Rajendran <email address hidden>
Date: Fri Dec 16 11:15:40 2022 -0500

    Enable kubelet upgrade with force option on AIO-SX

    This enable k8s kubelet upgrade process for an AIO-SX to
    start even if the node is in-test/degraded/failed/locked.

    Test Plan:
    PASS: no memory alarm and no "-f" option, ensure kubelet upgrade
          is allowed
    PASS: with memory alarm and no "-f" option, ensure kubelet upgrade
          is rejected
    PASS: with memory alarm and "-f" option, ensure kubelet upgrade
          is allowed

    Closes-Bug: 1999903

    Signed-off-by: Boovan Rajendran <email address hidden>
    Change-Id: Ia855c06b0887dddc61a1b39d04540cbe12fba6c1