[release-4.15] OCPBUGS-74300: Skip E2e: attach on previously attached volumes should work

[dfajmon]

https://issues.redhat.com/browse/OCPBUGS-74300
This test was never used and has been deprecated in versions 4.18 and later.
Continuation of openshift/kubernetes#2566

What type of PR is this?

/kind bug
/kind failing-test

What this PR does / why we need it:

Skip e2e: attach on previously attached volumes should work
This test was never used and has been deprecated in versions 4.18 and later.

Which issue(s) this PR is related to:

N/A

Special notes for your reviewer:

part of openshift/kubernetes#2569
cc @jsafrane

Does this PR introduce a user-facing change?

NONE

[openshift-ci-robot]

@dfajmon: This pull request references Jira Issue OCPBUGS-74300, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-74299 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

https://issues.redhat.com/browse/OCPBUGS-74300
This test was never used and has been deprecated in versions 4.18 and later.
Continuation of openshift/kubernetes#2566

What type of PR is this?

/kind bug
/kind failing-test

What this PR does / why we need it:

Skip e2e: attach on previously attached volumes should work
This test was never used and has been deprecated in versions 4.18 and later.

Which issue(s) this PR is related to:

N/A

Special notes for your reviewer:

part of openshift/kubernetes#2569
cc @jsafrane

Does this PR introduce a user-facing change?

NONE

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 openshift-eng/jira-lifecycle-plugin repository.

[dfajmon]

/retest-required

[dfajmon]

/jira refresh

[openshift-ci-robot]

@dfajmon: This pull request references Jira Issue OCPBUGS-74300, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.15.z) matches configured target version for branch (4.15.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-74299 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-74299 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0, 4.16.z
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

/jira 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 openshift-eng/jira-lifecycle-plugin repository.

[bertinatto]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto, dfajmon

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [bertinatto]
• test/extended/util/image/OWNERS [bertinatto]

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

[openshift-ci]

@dfajmon: all tests passed!

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-sigs/prow repository. I understand the commands that are listed here.

[radeore]

/verified by @radeore and CI

[openshift-ci-robot]

@radeore: This PR has been marked as verified by @radeore and CI.

Details

In response to this:

/verified by @radeore and CI

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@dfajmon: Jira Issue OCPBUGS-74300: Some pull requests linked via external trackers have merged:

• openshift/kubernetes#2569
• openshift/origin#30725

The following pull request, linked via external tracker, has not merged:

• openshift/origin#30727 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-74300 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

Details

In response to this:

https://issues.redhat.com/browse/OCPBUGS-74300
This test was never used and has been deprecated in versions 4.18 and later.
Continuation of openshift/kubernetes#2566

What type of PR is this?

/kind bug
/kind failing-test

What this PR does / why we need it:

Skip e2e: attach on previously attached volumes should work
This test was never used and has been deprecated in versions 4.18 and later.

Which issue(s) this PR is related to:

N/A

Special notes for your reviewer:

part of openshift/kubernetes#2569
cc @jsafrane

Does this PR introduce a user-facing change?

NONE

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 openshift-eng/jira-lifecycle-plugin repository.