Comment 0 for bug 2041686

StarlingX bug reporting guidelines:
Please use the template below when opening StarlingX bugs.

Brief Description
-----------------

when we perform multi k8s upgrade using orchestration method for the first k8s control-plane and kubelet it will upgrade successfully but when it continues to upgrade next k8s kubelet it will fail due to 200.006 alarm.

Severity
--------
Major

Steps to Reproduce
------------------
Upgrade kublet as part of the kubernets upgarde.

Expected Behavior
------------------
Write down what was expected after taking the steps written above

Actual Behavior
----------------
isolcpu_plugin is not running after kubelet upgrade.

Reproducibility
---------------
100%

System Configuration
--------------------
All controllers and workers

Branch/Pull Time/Commit
-----------------------
Master

Last Pass
---------

Timestamp/Logs
--------------
[sysadmin@controller-0 ~(keystone_admin)]$ sw-manager kube-upgrade-strategy show
Strategy Kubernetes Upgrade Strategy:
  strategy-uuid: 88e0b598-6abe-480f-972e-56b59dde0f4f
  controller-apply-type: serial
  storage-apply-type: serial
  worker-apply-type: serial
  default-instance-action: stop-start
  alarm-restrictions: strict
  current-phase: abort
  current-phase-completion: 100%
  state: aborted
  apply-result: failed
  apply-reason: alarms ['200.006'] from platform are present
  abort-result: success
  abort-reason:

Test Activity
-------------
Testing

Workaround
----------
Use systemd to unmask and start isolcpu_plugin. Use pmon-start to monitor isolcpu_plugin.