[release-4.13] OCPBUGS-77660: Skip E2e: attach on previously attached volumes should work

[dfajmon]

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

Backporting on request of @davegord. CI will fail on this PR too, tests need to be vendored to origin.
Cherry-picking from last PR was not possible due to merge conflicts.

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:

#2618 must be merged first to fix unit tests and verify checks.
cc @davegord @jsafrane

Does this PR introduce a user-facing change?

NONE

[openshift-ci-robot]

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

• expected the bug to target either version "4.13." or "openshift-4.13.", but it targets "4.12" instead
• expected dependent Jira Issue OCPBUGS-77660 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead
• expected dependent Jira Issue OCPBUGS-77660 to target a version in 4.14.0, 4.14.z, but it targets "4.13" 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-77661
This test was never used and has been deprecated in versions 4.18 and later.
Continuation of #2566

Backporting on request of @davegord. CI will fail on this PR too, tests need to be vendored to origin.

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:

cc @davegord @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.

[openshift-ci-robot]

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

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

• 93e59f5|UPSTREAM: : Skip e2e test: attach on previously attached volumes should work: 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]

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

• expected dependent Jira Issue OCPBUGS-74302 to target a version in 4.14.0, 4.14.z, but it targets "4.14" 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-77661
This test was never used and has been deprecated in versions 4.18 and later.
Continuation of #2566

Backporting on request of @davegord. CI will fail on this PR too, tests need to be vendored to origin.

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:

cc @davegord @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]

/jira refresh

[openshift-ci-robot]

@dfajmon: This pull request references Jira Issue OCPBUGS-77660, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.13.z) matches configured target version for branch (4.13.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-74302 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-74302 targets the "4.14.z" version, which is one of the valid target versions: 4.14.0, 4.14.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.

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.

[openshift-ci-robot]

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

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.13.z) matches configured target version for branch (4.13.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-74302 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-74302 targets the "4.14.z" version, which is one of the valid target versions: 4.14.0, 4.14.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.

Details

In response to this:

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

Backporting on request of @davegord. CI will fail on this PR too, tests need to be vendored to origin.

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:

cc @davegord @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]

/cherrypick release-4.12

[openshift-cherrypick-robot]

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

Details

In response to this:

/cherrypick release-4.12

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.

[dfajmon]

/retest

[openshift-ci-robot]

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

• expected dependent Jira Issue OCPBUGS-77468 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead
• expected dependent Jira Issue OCPBUGS-77468 to target a version in 4.14.0, 4.14.z, but it targets "4.13.z" 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.

Details

In response to this:

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

Backporting on request of @davegord. CI will fail on this PR too, tests need to be vendored to origin.
Cherry-picking from last PR was not possible due to merge conflicts.

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:

#2618 must be merged first to fix unit tests and verify checks.
cc @davegord @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

[dfajmon]

/jira refresh

[openshift-ci-robot]

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

• expected dependent Jira Issue OCPBUGS-77468 to target a version in 4.14.0, 4.14.z, but it targets "4.13.z" 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.

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.

[dfajmon]

/jira refresh

[bertinatto]

/lgtm
/label backport-risk-assessed
/override ci/prow/e2e-aws-ovn-serial
/retest-required

[openshift-ci]

@bertinatto: bertinatto unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers openshift-sustaining-engineers.

Details

In response to this:

/lgtm
/label backport-risk-assessed
/override ci/prow/e2e-aws-ovn-serial
/retest-required

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.

[benluddy]

/override ci/prow/e2e-aws-ovn-serial

[openshift-ci]

@benluddy: Overrode contexts on behalf of benluddy: ci/prow/e2e-aws-ovn-serial

Details

In response to this:

/override ci/prow/e2e-aws-ovn-serial

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

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:

• DOWNSTREAM_OWNERS

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

[bertinatto]

/remove-label backports/unvalidated-commits

[bertinatto]

/verified bypass

This will only be verified after the o/o bump

[openshift-ci-robot]

@bertinatto: The verified label has been added.

Details

In response to this:

/verified bypass

This will only be verified after the o/o bump

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

/retest-required

Remaining retests: 0 against base HEAD 7aa9360 and 2 for PR HEAD 93e59f5 in total

[benluddy]

/override ci/prow/e2e-aws-ovn-serial

[openshift-ci]

@benluddy: Overrode contexts on behalf of benluddy: ci/prow/e2e-aws-ovn-serial

Details

In response to this:

/override ci/prow/e2e-aws-ovn-serial

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.

[dfajmon]

/retest

[benluddy]

/override ci/prow/e2e-aws-ovn-serial
/override ci/prow/e2e-aws-ovn-serial
/override ci/prow/e2e-aws-ovn-serial

[benluddy]

🔨

[openshift-ci]

@benluddy: Overrode contexts on behalf of benluddy: ci/prow/e2e-aws-ovn-serial

Details

In response to this:

/override ci/prow/e2e-aws-ovn-serial
/override ci/prow/e2e-aws-ovn-serial
/override ci/prow/e2e-aws-ovn-serial

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.

[openshift-ci]

@dfajmon: The following test 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-ovn-serial	93e59f5	link	true	/test e2e-aws-ovn-serial

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.

[openshift-ci-robot]

@dfajmon: Jira Issue Verification Checks: Jira Issue OCPBUGS-77660
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-77660 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

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

Backporting on request of @davegord. CI will fail on this PR too, tests need to be vendored to origin.
Cherry-picking from last PR was not possible due to merge conflicts.

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:

#2618 must be merged first to fix unit tests and verify checks.
cc @davegord @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.

[openshift-cherrypick-robot]

@dfajmon: new pull request created: #2657

Details

In response to this:

/cherrypick release-4.12

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.

[openshift-merge-robot]

Fix included in release 4.13.0-0.nightly-2026-04-30-153345