Bug 2071941: Replace collect-profile jobs that haven't completed

[perdasilva]

Problem: The collect-profiles job should only take a few seconds to
run. There are instances, such as when the pod cannot be scheduled,
where the job will not complete in a reasonable amount of time. If
enough jobs are scheduled but unable to run, the number of
scheduled jobs can exceed pod quota limits.

Solution: Given that the collect-profiles job should only take a few
seconds to run and that the job is scheduled to run every 15 minutes,
set the collect-profiles cronJob's spec.concurrencyPolicy to
"Replace" so that only one active collect-profiles pod exists at any
time.

[openshift-ci]

@perdasilva: This pull request references Bugzilla bug 2071941, which is invalid:

• expected dependent Bugzilla bug 2055861 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
• expected dependent Bugzilla bug 2055861 to target a release in 4.10.0, 4.10.z, but it targets "4.11.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Bug 2071941: Replace collect-profile jobs that haven't completed

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[perdasilva]

/cherry-pick release-4.10

[openshift-cherrypick-robot]

@perdasilva: once the present PR merges, I will cherry-pick it on top of relase-4.10 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick relase-4.10

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[perdasilva]

/cherry-pick release-4.10

[openshift-cherrypick-robot]

@perdasilva: once the present PR merges, I will cherry-pick it on top of release-4.10 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.10

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: perdasilva
To complete the pull request process, please assign anik120 after the PR has been reviewed.
You can assign the PR to them by writing /assign @anik120 in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[perdasilva]

/hold wait until next week - 4.9 branch is picky atm

[perdasilva]

/test e2e-gcp

[openshift-ci]

@perdasilva: This pull request references Bugzilla bug 2071941, which is invalid:

• expected the bug to target the "4.10.z" release, but it targets "4.9.z" instead
• expected dependent Bugzilla bug 2055861 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Bug 2071941: Replace collect-profile jobs that haven't completed

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci]

@perdasilva: This pull request references Bugzilla bug 2071941, which is invalid:

• expected the bug to target the "4.9.z" release, but it targets "4.10.z" instead
• expected dependent Bugzilla bug 2055861 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
• expected dependent Bugzilla bug 2055861 to target a release in 4.10.0, 4.10.z, but it targets "4.11.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Bug 2071941: Replace collect-profile jobs that haven't completed

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci]

@perdasilva: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-console-olm	48f533d	link	true	/test e2e-aws-console-olm
ci/prow/e2e-upgrade	48f533d	link	true	/test e2e-upgrade
ci/prow/e2e-gcp	48f533d	link	true	/test e2e-gcp
ci/prow/unit-api	48f533d	link	true	/test unit-api
ci/prow/e2e-aws-olm	48f533d	link	true	/test e2e-aws-olm
ci/prow/unit-registry	48f533d	link	true	/test unit-registry
ci/prow/unit-olm	48f533d	link	true	/test unit-olm
ci/prow/verify	48f533d	link	true	/test verify
ci/prow/images	48f533d	link	true	/test images

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.