From 57ff6abf9b585c6c9ec8a454da665feb8fc655a5 Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Thu, 12 Nov 2020 16:45:42 -0800 Subject: [PATCH] ci-operator/step-registry/gather/core-dump: 10m active_deadline_seconds Like 3c915e2f0c (ci-operator/step-registry/openshift/e2e/test: Add 2h active_deadline_seconds, 2020-10-09, #12647), but for the gather-core-dump step. This helps hold time to run futher gathers and tear down the cluster under test, if gather-core-dump gets hung up, like it did for over 2h here [1]: $ curl -s https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-update-keys/25/pull-ci-openshift-cluster-update-keys-master-e2e-aws/1326950727196610560/build-log.txt | grep -A2 'Executing pod.*gather-core-dump' 2020/11/12 20:02:15 Executing pod "e2e-aws-gather-core-dump" 2020/11/12 20:02:42 Container cp-secret-wrapper in pod e2e-aws-gather-core-dump completed successfully {"component":"entrypoint","file":"prow/entrypoint/run.go:165","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Process did not finish before 4h0m0s timeout","severity":"error","time":"2020-11-12T22:11:29Z"} [1]: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-update-keys/25/pull-ci-openshift-cluster-update-keys-master-e2e-aws/1326950727196610560 --- .../step-registry/gather/core-dump/gather-core-dump-ref.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/ci-operator/step-registry/gather/core-dump/gather-core-dump-ref.yaml b/ci-operator/step-registry/gather/core-dump/gather-core-dump-ref.yaml index c2031589e5769..9c1dac9a8c353 100644 --- a/ci-operator/step-registry/gather/core-dump/gather-core-dump-ref.yaml +++ b/ci-operator/step-registry/gather/core-dump/gather-core-dump-ref.yaml @@ -3,6 +3,7 @@ ref: optional_on_success: true from: cli commands: gather-core-dump-commands.sh + active_deadline_seconds: 600 resources: requests: cpu: 300m