StarlingX

  1. Bug #2041686
  2. Activity log

Activity log for bug #2041686

Date Who What changed Old value New value Message
2023-10-27 16:33:17 Gleb Aronsky bug added bug
2023-10-27 16:36:50 OpenStack Infra starlingx: status New In Progress
2023-10-27 16:42:52 Gleb Aronsky summary controller-0 is degraded due to the failure of its isolcpu_plugi controller-0 is degraded due to the failure of its isolcpu_plugin
2023-10-27 18:04:14 OpenStack Infra starlingx: status In Progress Fix Released
2023-11-10 06:09:49 Ghada Khalil starlingx: importance Undecided Medium
2023-11-14 14:48:44 Ghada Khalil starlingx: assignee Gleb Aronsky (gleb-aronsky)
2023-11-14 14:49:04 Ghada Khalil tags stx.9.0 stx.config stx.containers
2023-11-14 14:49:20 Ghada Khalil description 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. 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.