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

Missing default value for maxUnhealthy under machinehealthcheck CR

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • In Progress
    • Bug Fix
    • Hide
      * Before this update, the `MachineHealthCheck` custom resource (CR) did not show the default value for the `maxUnhealthy` field. With this release, the CR also documents the value it defaults to when not set. (link:https://issues.redhat.com/browse/OCPBUGS-61096[OCPBUGS-61096])
      Show
      * Before this update, the `MachineHealthCheck` custom resource (CR) did not show the default value for the `maxUnhealthy` field. With this release, the CR also documents the value it defaults to when not set. (link: https://issues.redhat.com/browse/OCPBUGS-61096 [ OCPBUGS-61096 ])
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-60901. The following is the description of the original issue:
      —
      Description of problem:

      The command oc explain machinehealthchecks.machine.openshift.io.spec.maxUnhealthy does not show the default maxUnhealthy value:

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

      openshift 4.19+

       

      $ oc explain machinehealthchecks.machine.openshift.io.spec.maxUnhealthy 


GROUP:      machine.openshift.io
KIND:       MachineHealthCheck
VERSION:    v1beta1

FIELD: maxUnhealthy <Object>


DESCRIPTION:
    Any farther remediation is only allowed if at most "MaxUnhealthy" machines
    selected by
    "selector" are not healthy.
    Expects either a postive integer value or a percentage value.
    Percentage values must be positive whole numbers and are capped at 100%.
    Both 0 and 0% are valid and will block all remediation.


Only documentation has the default value mentioned.
Customer or support engineers who rely on CLI documentation, will not get complete idea.Shall I raise BUG or RFE to address this gap?    

      Actual results:

      The default value is missing

      Expected results:

      Expecting default value i.e. 100%

      Additional info:

          Only official documentation has the default value mentioned. Customer or support engineers who rely on CLI documentation, will not get complete idea.

              rh-ee-cschlott Christian Schlotter
              rhn-support-dpateriy Divyam Pateriya
              None
              None
              Zhaohua Sun Zhaohua Sun
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: