-
Bug
-
Resolution: Done-Errata
-
Undefined
-
4.18.0, 4.19.0
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:
- clones
-
OCPBUGS-54431 NodePool ignition tokens pile up due to reset of expiration timestamp
-
- Verified
-
- is blocked by
-
OCPBUGS-54431 NodePool ignition tokens pile up due to reset of expiration timestamp
-
- Verified
-
- links to
-
RHBA-2025:4019 OpenShift Container Platform 4.18.z bug fix update