VIM orchestrator unlocks the host when kubelet upgrade is in progress
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Vanathi Selvaraju |
Bug Description
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-
sw-manager kube-upgrade-
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.
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.
Test Activity
-------------
System Test
Workaround
----------
Unlock the host(which was failing to unlock) manually.
retrigger k8s upgrade.
Changed in starlingx: | |
status: | New → In Progress |
Changed in starlingx: | |
importance: | Undecided → Medium |
tags: | added: stx.9.0 stx.nfv |
tags: | added: stx.update |
Changed in starlingx: | |
assignee: | nobody → Vanathi Selvaraju (vselvara) |
Fix proposed to branch: master /review. opendev. org/c/starlingx /nfv/+/ 901767
Review: https:/