Skip to content

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

Open
dfajmon wants to merge 2 commits intoopenshift:release-4.14from
dfajmon:skip-attach-volumes-test-4.14
Open

[release-4.14] OCPBUGS-74300: Skip E2e: attach on previously attached volumes should work#30727
dfajmon wants to merge 2 commits intoopenshift:release-4.14from
dfajmon:skip-attach-volumes-test-4.14

Conversation

@dfajmon
Copy link
Contributor

@dfajmon dfajmon commented Jan 27, 2026

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#2570
cc @jsafrane

Does this PR introduce a user-facing change?

NONE

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 27, 2026
@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Jan 27, 2026
@openshift-ci-robot
Copy link

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

  • expected the bug to target either version "4.14." or "openshift-4.14.", but it targets "4.15.0" instead
  • 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
  • expected dependent Jira Issue OCPBUGS-74299 to target a version in 4.15.0, 4.15.z, but it targets "4.16.0" 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#2570
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.

@openshift-ci openshift-ci bot added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Jan 27, 2026
@openshift-ci openshift-ci bot requested review from csrwng and deads2k January 27, 2026 12:46
…hould work

This test was never used and has been deprecated in versions 4.18 and later.
@dfajmon dfajmon force-pushed the skip-attach-volumes-test-4.14 branch from 67d178e to ac47320 Compare February 6, 2026 11:22
@openshift-ci openshift-ci bot added e2e-images-update Related to images used by e2e tests vendor-update Touching vendor dir or related files labels Feb 6, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 6, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details Needs approval from an approver in each of these files:

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

@dfajmon
Copy link
Contributor Author

dfajmon commented Feb 6, 2026

/retest-required

@bertinatto
Copy link
Member

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 6, 2026

@dfajmon: 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-ovn-serial ac47320 link true /test e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-fips ac47320 link true /test e2e-aws-ovn-fips
ci/prow/e2e-gcp-ovn ac47320 link true /test e2e-gcp-ovn

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

e2e-images-update Related to images used by e2e tests jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. kind/bug Categorizes issue or PR as related to a bug. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. vendor-update Touching vendor dir or related files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants