Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-27246

Unhealthy conditions table should put Type as first column on MachineHealthCheck details page

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • 4.16.0
    • 4.15
    • Management Console
    • None
    • Moderate
    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, the *Type* column was not first on the condition table on the *MachineHealthCheck detail* page. With this update, the *Type* is now listed first on the condition table. (link:https://issues.redhat.com/browse/OCPBUGS-27246[*OCPBUGS-27246*])
      Show
      * Previously, the *Type* column was not first on the condition table on the *MachineHealthCheck detail* page. With this update, the *Type* is now listed first on the condition table. (link: https://issues.redhat.com/browse/OCPBUGS-27246 [* OCPBUGS-27246 *])
    • Enhancement
    • Done

      Description of problem:

      There is an 'Unhealthy Conditions' table on MachineHealthCheck details page, currently the first column is 'Status'， user care more about Type then its Status

      Version-Release number of selected component (if applicable):

      4.15.0-0.nightly-2024-01-16-113018    

      How reproducible:

      Always

      Steps to Reproduce:

      1. go to any MHC details page and check 'Unhealthy Conditions' table
2.
3.

      Actual results:

      in the table, 'Type' is the last column

      Expected results:

      we should put 'Type' as the first column since this is the most important factor user care

for comparsion, we can check the 'Conditions' table on ClusterOperators details page, the order is Type -> Status -> other info which is very user friendly

      Additional info:

              cajieh Cyril Ajieh
              rhn-support-yapei YaDan Pei
              Xiyun Zhao Xiyun Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: