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

MachineConfigNode condition Cordoned is used to show status of both cordon and uncordon

XMLWordPrintable

    • +
    • No
    • MCO Sprint 246
    • 1
    • False
    • Hide

      None

      Show
      None
    • N/A: tech preview feature fix in same release
    • Release Note Not Required
    • In Progress

      When we apply a machine config with additional ssh key info, this action only needs to uncordon the node, when uncordon is happening, condition Cordoned = True. it will make the user confuse. maybe we can refine this design to show status of cordon/uncordon separately  

       

      lastTransitionTime: '2023-11-28T16:53:58Z'   message: 'Action during previous iteration: (Un)Cordoned node. The node is reporting     Unschedulable = false'   reason: UpdateCompleteCordoned   status: 'False'   type: Cordoned  

              cdoern@redhat.com Charles Doern
              rhn-support-rioliu Rio Liu
              Rio Liu Rio Liu
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: