system kube-upgrade-start reports the wrong health query
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Al Bailey |
Bug Description
Brief Description
-----------------
The kube-upgrade-start command reports the wrong CLI command to use when it fails the health query
Severity
--------
Minor
Steps to Reproduce
------------------
Attempt a kubernetes upgrade while a kubernetes app is in failed state, following the steps here :https:/
Expected Behavior
------------------
Should report the correct procedure to move forward
"System is not in a valid state for kubernetes upgrade. Run system health-
Actual Behavior
----------------
Reports the wrong health query, which will not necessarily indicate the reason for the failure.
"System is not in a valid state for kubernetes upgrade. Run system health-query for more details."
Reproducibility
---------------
This is reproducable, but the scenario of having a broken kubernetes app is not expected, and doing an kubernetes upgrade is incredibly infrequent.
System Configuration
-------
STD duplex
Branch/Pull Time/Commit
-------
Nov 3, 2020
Last Pass
---------
Unknown
Timestamp/Logs
--------------
N/A
This is a CLI reporting the wrong string.
Test Activity
-------------
Developer Testing
Workaround
----------
Use the correct CLI command
Changed in starlingx: | |
assignee: | nobody → Al Bailey (albailey1974) |
tags: | added: stx.5.0 stx.update |
Changed in starlingx: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Fix proposed to branch: master /review. opendev. org/761471
Review: https:/