bug 2008181: UPSTREAM: 105205: e2e scheduling priorities: do not reference control loop variable

[ingvagabund]

Otherwise, nodeNameToPodList[nodeName] list will have all its references
identical (corresponding to the control variable reference).
Thus, making all the pods in the list identical.

Backporting kubernetes#105205

[openshift-ci]

@ingvagabund: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

UPSTREAM: 105205: e2e scheduling priorities: do not reference control loop variable

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-robot]

@ingvagabund: the contents of this pull request could be automatically validated.

The following commits are valid:

• 4197e72|UPSTREAM: 105205: e2e scheduling priorities: do not reference control loop variable: the upstream PR kubernetes/kubernetes#105205 has merged

[ingvagabund]

/bugzilla refresh

[openshift-ci]

@ingvagabund: This pull request references Bugzilla bug 2008181, which is invalid:

• expected the bug to target the "4.9.0" release, but it targets "---" instead
• expected Bugzilla bug 2008181 to depend on a bug targeting a release in 4.10.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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.

In response to this:

/bugzilla refresh

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]

@ingvagabund: This pull request references Bugzilla bug 2008181, which is invalid:

• expected the bug to target the "4.9.0" release, but it targets "---" instead
• expected Bugzilla bug 2008181 to depend on a bug targeting a release in 4.10.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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.

In response to this:

bug 2008181: UPSTREAM: 105205: e2e scheduling priorities: do not reference control loop variable

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.

[ingvagabund]

4.9 final freeze is over. Let's wait until 4.9.z is open.

[damemi]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

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

[soltysh]

/hold
The general policy is to get this through an upstream pick and merged during our monthly bumps.

[openshift-ci]

@ingvagabund: 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-openstack-csi-manila	4197e72	link	false	/test e2e-openstack-csi-manila
ci/prow/e2e-aws-csi	4197e72	link	false	/test e2e-aws-csi
ci/prow/e2e-openstack-csi-cinder	4197e72	link	false	/test e2e-openstack-csi-cinder
ci/prow/e2e-gcp-upgrade	4197e72	link	true	/test e2e-gcp-upgrade

Full PR test history. Your PR dashboard.

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.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

/bugzilla refresh

The requirements for Bugzilla bugs have changed, recalculating validity.

[openshift-ci]

@openshift-bot: This pull request references Bugzilla bug 2008181, which is invalid:

• expected the bug to target the "4.9.z" release, but it targets "---" instead
• expected Bugzilla bug 2008181 to depend on a bug targeting a release in 4.10.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

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.

In response to this:

/bugzilla refresh

The requirements for Bugzilla bugs have changed, recalculating validity.

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-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale