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

hypershift worker nodes replace upgrade from 4.12 to 4.13 stuck

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • 4.13
    • HyperShift
    • 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:

      There is an SDN test case pod with terminationGracePeriodSeconds: 30 that caused the node to fail to be drained

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

       

      How reproducible:

      1. prepare one 4.12 hypershift env
      2. deploy a pod/deployment with terminationGracePeriodSeconds: 30
         attach the example yaml below
      3. upgrade nodepool release to 4.13
      4. oc --kubeconfig=guest-cluster.kubeconfig get node to check the node hanging  status

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

      upgrade stuck in the process

      Expected results:

      nodepool upgrade successfully

      Additional info:

       

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

                Created:
                Updated:
                Resolved: