system kube-upgrade-start reports the wrong health query

Bug #1902804 reported by Al Bailey
6
This bug affects 1 person
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://docs.starlingx.io/configuration/k8s_upgrade.html

Expected Behavior
------------------
Should report the correct procedure to move forward

"System is not in a valid state for kubernetes upgrade. Run system health-query-kube-upgrade for more details."

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

Al Bailey (albailey1974)
Changed in starlingx:
assignee: nobody → Al Bailey (albailey1974)
Ghada Khalil (gkhalil)
tags: added: stx.5.0 stx.update
Changed in starlingx:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to config (master)

Fix proposed to branch: master
Review: https://review.opendev.org/761471

Changed in starlingx:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to config (master)

Reviewed: https://review.opendev.org/761471
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=619a16c28b68b10a8d16270e5c6a46f46d79bea0
Submitter: Zuul
Branch: master

commit 619a16c28b68b10a8d16270e5c6a46f46d79bea0
Author: albailey <email address hidden>
Date: Wed Nov 4 17:23:55 2020 -0600

    Fix the message when system kube-upgrade-start fails

    Previously if a kube-upgrade-start failed the health check
    it would incorrectly state:
      System is not in a valid state for kubernetes upgrade.
      Run system health-query for more details.

    However that command does not show all the reasons that could
    block the kube-upgrade-start, such as invalid kubernetes apps.

    The output has been changed to:
      System is not in a valid state for kubernetes upgrade.
      Run system health-query-kube-upgrade for more details.

    Change-Id: Id2717dcfb355e2a854ffbd8e04862b29b00248df
    Closes-Bug: 1902804
    Signed-off-by: albailey <email address hidden>

Changed in starlingx:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.