VIM orchestrator unlocks the host when kubelet upgrade is in progress

[Vanathi Selvaraju]

Brief Description
-----------------
K8s upgrade using VIM orchestrator failed in the host unlock phase as kubelet upgrade was
still ongoing.

Severity
--------

Major

Steps to Reproduce
------------------
sw-manager kube-upgrade-strategy create --to-version 1.22.5
sw-manager kube-upgrade-strategy apply

Expected Behavior
------------------
k8s upgrade should be successful

Actual Behavior
----------------
K8s upgrade failed in host unlock phase.

Reproducibility
---------------
Seen occasionally

System Configuration
--------------------
Standard configuration(with controller-0 , controller-1 and a worker)

Branch/Pull Time/Commit
-----------------------
2023-11-14_22-20-52

Timestamp/Logs
--------------

sysinv 2023-11-17 03:43:17.152 45437 INFO sysinv.api.controllers.v1.host [-] host unlock check didn't pass, so set the ihost_a ction (lock--) back to None and re-raise the exception
sysinv 2023-11-17 03:43:17.166 45437 WARNING wsme.api [-] Client-side error: Can not unlock controller-0 while upgrading kubelet. Wait for kubelet upgrade to complete.: wsme.exc.ClientSideError: Can not unlock controller-0 while upgrading kubelet. Wait for kubelet upgrade to complete.

Test Activity
-------------
System Test

Workaround
----------

Unlock the host(which was failing to unlock) manually.
retrigger k8s upgrade.