WIP: UPSTREAM: 117804: Refactor FindAttachablePluginBySpec out of CSI code…

[rphillips]

Testing this PR with graceful shutdowns.

[openshift-ci-robot]

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

The following commits are valid:

• 37a1f7b|UPSTREAM: 117804: Refactor FindAttachablePluginBySpec out of CSI code path: the upstream PR kubernetes/kubernetes#117804 has merged

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

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

The following commits are valid:

• a2bfcf3|UPSTREAM: 117804: Refactor FindAttachablePluginBySpec out of CSI code path: the upstream PR kubernetes/kubernetes#117804 has merged

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

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

The following commits are valid:

• a2bfcf3|UPSTREAM: 117804: Refactor FindAttachablePluginBySpec out of CSI code path: the upstream PR kubernetes/kubernetes#117804 has merged

The following commits could not be validated and must be approved by a top-level approver:

• 88c0471|UPSTREAM: : debug: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

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

The following commits are valid:

• f3ee1f1|UPSTREAM: 117804: Refactor FindAttachablePluginBySpec out of CSI code path: the upstream PR kubernetes/kubernetes#117804 has merged

The following commits could not be validated and must be approved by a top-level approver:

• 0eed6ba|UPSTREAM: : debug: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

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

The following commits are valid:

• f3ee1f1|UPSTREAM: 117804: Refactor FindAttachablePluginBySpec out of CSI code path: the upstream PR kubernetes/kubernetes#117804 has merged

The following commits could not be validated and must be approved by a top-level approver:

• 0eed6ba|UPSTREAM: : debug: does not specify an upstream backport in the commit message
• 2f6750f|UPSTREAM: : add change to podcache: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

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

The following commits are valid:

• f3ee1f1|UPSTREAM: 117804: Refactor FindAttachablePluginBySpec out of CSI code path: the upstream PR kubernetes/kubernetes#117804 has merged

The following commits could not be validated and must be approved by a top-level approver:

• 0eed6ba|UPSTREAM: : debug: does not specify an upstream backport in the commit message
• 6b121b7|UPSTREAM: : add change to podcache: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

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

The following commits are valid:

• f78fb5c|UPSTREAM: 117804: Refactor FindAttachablePluginBySpec out of CSI code path: the upstream PR kubernetes/kubernetes#117804 has merged

The following commits could not be validated and must be approved by a top-level approver:

• 9640364|UPSTREAM: : add change to podcache: does not specify an upstream backport in the commit message
• f950716|UPSTREAM: : debug: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rphillips
Once this PR has been reviewed and has the lgtm label, please assign tkashem for approval. For more information see the Kubernetes Code Review Process.

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

[openshift-ci]

@rphillips: 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-csi	9640364	link	false	/test e2e-aws-csi
ci/prow/verify	9640364	link	true	/test verify
ci/prow/e2e-aws-ovn-fips	9640364	link	true	/test e2e-aws-ovn-fips
ci/prow/unit	9640364	link	true	/test unit
ci/prow/e2e-aws-ovn-serial	9640364	link	true	/test e2e-aws-ovn-serial

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]

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

[openshift-merge-robot]

PR needs rebase.

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]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.