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

no rolling update with nodepool.spec.nodeDrainTimeout

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 4.14
    • HyperShift
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • No
    • None
    • None
    • Rejected
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      OCP-48673 for HOSTEDCP-303 failed with no rolling update of nodepool worker nodes when nodepool.spec.nodeDrainTimeout was set to "1m"

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

      4.14

      How reproducible:

      100%

      Steps to Reproduce:

      # run ocp 48673 in extended-platform-tests 
      ./bin/extended-platform-tests run all --dry-run | grep 48673  | ./bin/extended-platform-tests run --timeout=90m -f - 
      
      Or referring steps in https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-48673

      Actual results:

      step 8/step 9 in OCP-48673: no change for awsmachine when nodepool.spec.nodeDrainTimeout was set

      Expected results:

       step 8/step 9 in OCP-48673: Rolling upgrade is triggered

      Additional info:

      $ oc get np 48673np-swzzigtu -n clusters -ojsonpath='{.spec.nodeDrainTimeout}' 
      1m

              agarcial@redhat.com Alberto Garcia Lamela
              rhn-support-heli He Liu
              None
              None
              Jie Zhao Jie Zhao
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: