sysinv allows k8s upgrade to start with platform memory alarm, but doesn't allow kubelet upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Boovan Rajendran |
Bug Description
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.
Changed in starlingx: | |
assignee: | nobody → Boovan Rajendran (brajendr) |
Changed in starlingx: | |
importance: | Undecided → Low |
tags: | added: stx.containers stx.update |
tags: | added: stx.9.0 |
Fix proposed to branch: master /review. opendev. org/c/starlingx /config/ +/867982
Review: https:/