Bug 1957886

Summary:	In k8s 1.21 bump TTLAfterFinished is disabled
Product:	OpenShift Container Platform	Reporter:	Maciej Szulik <maszulik>
Component:	kube-controller-manager	Assignee:	Maciej Szulik <maszulik>
Status:	CLOSED ERRATA	QA Contact:	zhou ying <yinzhou>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.8	CC:	aos-bugs, mfojtik, stbenjam
Target Milestone:	---
Target Release:	4.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-10-18 17:31:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Maciej Szulik 2021-05-06 17:38:48 UTC

In https://github.com/openshift/origin/pull/26054 we temporarily disabled the following tests:

[sig-apps] [Feature:TTLAfterFinished] job should be deleted once it finishes after TTL seconds

example failures can be noticed in:

https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/26054/pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6/1390271717254893568

Comment 1 Maciej Szulik 2021-05-06 17:48:09 UTC

Looks like in metal env the time is off, such that deleteTime is sooner than expiryTime.

Comment 2 Michal Fojtik 2021-06-05 18:29:07 UTC

This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.

Comment 4 Stephen Benjamin 2021-07-07 13:46:41 UTC

This still fails quite often on IPv6 -- it looks like there's no NTP because we don't have outbound internet access. https://github.com/openshift-metal3/dev-scripts/pull/1274 sets up a local chronyd for the cluster that it can access, going to see if that improves the test pass rate.

Comment 7 zhou ying 2021-08-03 06:31:12 UTC

Can't see same error in https://search.ci.openshift.org/?search=job+should+be+deleted+once+it+finishes+after+TTL+&maxAge=168h&context=1&type=bug%2Bjunit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job.  will verify this.

Comment 10 errata-xmlrpc 2021-10-18 17:31:03 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:3759