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

MCO takes the lease ownership (~5 mins) after API server is up

XMLWordPrintable

    • No
    • MCO Sprint 233
    • 1
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      We are trying out 4.12.3 and observe that once the cluster is stopped (shutdown) and started again it takes bit of time for MCO to get the lease (~5 mins) after API server is up,

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

      $ oc version
      Client Version: 4.12.3
      Kustomize Version: v4.5.7
      

      How reproducible:

      Every single time for us (CRC team) where we provision the openshift cluster and then use it for each run.

      Steps to Reproduce:

      - Create a single node cluster and shut it down
      - Start it again and as soon as apiserver is up edit/patch the pull secret
      - Check the MCD logs and you will find the timestamp around how long it take to get the lease ownership (In our case it is ~5 mins) 

      Actual results:

      Takes around ~5 mins

      Expected results:

      shouldn't take more than 40-50 sec

      Additional info:

      Only workaround to make it faster is to remove old lease
      
      oc delete lease machine-config-controller -n openshift-machine-config-operator

            jkyros@redhat.com John Kyros
            prkumar@redhat.com Praveen Kumar
            Rio Liu Rio Liu
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: