Kube Upgrade needs to raise/clear appropriate alarms based on its activity
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
John Kung |
Bug Description
Brief Description
-----------------
There is an alarm defined for kube upgrade in progress
900.007 defined in fm-api ( FM_ALARM_
however there is no code in sysinv to raise or clear that alarm.
Would be good to raise/clear the alarm so we are consistent between upgrades, patching, firmware
and k8s upgrade.
Note: When this is fixed, the VIM kube upgrade orchestration and DC kube upgrade orchestration should
also be re-tested to ensure the alarm does not block their execution.
Severity
--------
Minor: potential missing alarm; during orchestration there is a raised orchestration alarm
to indicate the state kube upgrade in progress; however, not if performed manually.
Steps to Reproduce
------------------
Start a kubernetes upgrade and check fm.
system kube-upgrade-start <some version>
fm alarm-list
Steps for setting up env to run a kubernetes upgrade are here:
https:/
Expected Behavior
------------------
there should be an alarm (900.007)
Actual Behavior
----------------
no alarm for kube upgrade exists
Reproducibility
---------------
100% reproducible
System Configuration
-------
Can be done in any env that supports kube upgrade. (AIO-SX, AIO-DX or STD-DX)
Branch/Pull Time/Commit
-------
June 14, 2021
Last Pass
---------
N/A
Timestamp/Logs
--------------
N/A
There are no logs, because this is an enhancement rather than an error or a failure.
Test Activity
-------------
Code Inspection
Workaround
----------
No need for a workaround, although the alarm could be manually raised.
Changed in starlingx: | |
assignee: | nobody → John Kung (john-kung) |
tags: | added: stx.6.0 stx.distcloud stx.update |
Changed in starlingx: | |
importance: | Undecided → Low |
Fix proposed to branch: master /review. opendev. org/c/starlingx /config/ +/800936
Review: https:/