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

NodePool ignition tokens pile up due to reset of expiration timestamp

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • 4.18.0
    • 4.18.0, 4.19.0
    • HyperShift
    • Important
    • None
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Prevent resetting the node pool token expiration timestamp annotation if it has already been set.
    • Done

      This is a clone of issue OCPBUGS-54431. The following is the description of the original issue:

      Description of problem:

          Due to how the 2 hour delay is set via an annotation on the ignition token, if the reconcile loop runs more than every 2 hours, the timestamp is reset and the expiration date is never reached, thus cleanup does not occur.

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

          

      How reproducible:

          

      Steps to Reproduce:

          1.Deploy a cluster with Hypershift Operator
          2.Update the nodepool(s) to cause a new ignition token(s) to be generate
          3.When the reconcile loop in HO runs more often than every 2 hours, watch the expiration timestamp annotation.
          

      Actual results:

          Timestamp is reset instead of allowing the initial 2 hour window to expire

      Expected results:

          Timestamp is not reset so that the 2 hour window set by the timestamp can expire and the ignition-server performs the cleanup

      Additional info:

          

              pamelachristie Pamela Schaefer (Inactive)
              openshift-crt-jira-prow OpenShift Prow Bot
              Pamela Schaefer Pamela Schaefer (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: