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

[dfajmon]

https://issues.redhat.com/browse/OCPBUGS-74302
This test was never used and has been deprecated in versions 4.18 and later.
Continuation of #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:

cc @jsafrane

Does this PR introduce a user-facing change?

NONE

[openshift-ci-robot]

@dfajmon: This pull request references Jira Issue OCPBUGS-74302, 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-74300 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-74302
This test was never used and has been deprecated in versions 4.18 and later.

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 @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:

• eaaa072|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-74302, which is invalid:

• expected dependent Jira Issue OCPBUGS-74300 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.

Details

In response to this:

https://issues.redhat.com/browse/OCPBUGS-74302
This test was never used and has been deprecated in versions 4.18 and later.
Continuation of #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:

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]

/retest-required

[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:

• 29db8ca|UPSTREAM: : Bump vendor: does not specify an upstream backport in the commit message
• 829f739|UPSTREAM: : Update vendor: does not specify an upstream backport in the commit message
• eaaa072|UPSTREAM: : Skip e2e test: attach on previously attached volumes should work: does not specify an upstream backport in the commit message
• f5ace67|UPSTREAM: : Disable AZURE blobdisk tests: 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: 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:

• 60a122b|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.

[bertinatto]

/override verify
Failure not related to this PR

/override ci/prow/e2e-aws-ovn-serial
The failure here is what this PR is trying to fix, but we need to bump o/o to have effect

/remove-label backports/unvalidated-commits
/label backport-risk-assessed
/lgtm

[openshift-ci]

@bertinatto: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

• verify

Only the following failed contexts/checkruns were expected:

• ci/prow/artifacts
• ci/prow/e2e-aws-crun-wasm
• ci/prow/e2e-aws-ovn-cgroupsv2
• ci/prow/e2e-aws-ovn-crun
• ci/prow/e2e-aws-ovn-fips
• ci/prow/e2e-aws-ovn-serial
• ci/prow/e2e-gcp
• ci/prow/e2e-gcp-ovn-upgrade
• ci/prow/images
• ci/prow/integration
• ci/prow/k8s-e2e-conformance-aws
• ci/prow/k8s-e2e-gcp-ovn
• ci/prow/k8s-e2e-gcp-serial
• ci/prow/unit
• ci/prow/verify
• ci/prow/verify-commits
• pull-ci-openshift-kubernetes-master-artifacts
• pull-ci-openshift-kubernetes-master-e2e-aws-crun-wasm
• pull-ci-openshift-kubernetes-master-e2e-aws-ovn-cgroupsv2
• pull-ci-openshift-kubernetes-master-e2e-aws-ovn-crun
• pull-ci-openshift-kubernetes-master-e2e-aws-ovn-fips
• pull-ci-openshift-kubernetes-master-e2e-gcp
• pull-ci-openshift-kubernetes-master-e2e-gcp-ovn-upgrade
• pull-ci-openshift-kubernetes-master-images
• pull-ci-openshift-kubernetes-master-integration
• pull-ci-openshift-kubernetes-master-k8s-e2e-conformance-aws
• pull-ci-openshift-kubernetes-master-k8s-e2e-gcp-ovn
• pull-ci-openshift-kubernetes-master-k8s-e2e-gcp-serial
• pull-ci-openshift-kubernetes-master-unit
• pull-ci-openshift-kubernetes-master-verify
• pull-ci-openshift-kubernetes-master-verify-commits
• pull-ci-openshift-kubernetes-release-4.12-e2e-aws-ovn-serial
• tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/override verify
Failure not related to this PR

/override ci/prow/e2e-aws-ovn-serial
The failure here is what this PR is trying to fix, but we need to bump o/o to have effect

/remove-label backports/unvalidated-commits
/label backport-risk-assessed
/lgtm

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

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 [bertinatto]

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

[bertinatto]

/override ci/prow/verify
Failure not related to this PR

/override ci/prow/e2e-aws-ovn-serial
The failure here is what this PR is trying to fix, but we need to bump o/o to have effect

[openshift-ci]

@bertinatto: Overrode contexts on behalf of bertinatto: ci/prow/e2e-aws-ovn-serial, ci/prow/verify

Details

In response to this:

/override ci/prow/verify
Failure not related to this PR

/override ci/prow/e2e-aws-ovn-serial
The failure here is what this PR is trying to fix, but we need to bump o/o to have effect

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 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	60a122b	link	true	/test e2e-aws-ovn-serial
ci/prow/verify	60a122b	link	true	/test verify

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.

[duanwei33]

/verified later @duanwei33
(Will check the CI result when all PRs are merged)

[openshift-ci-robot]

@duanwei33: This PR has been marked to be verified later by @duanwei33.

Details

In response to this:

/verified later @duanwei33
(Will check the CI result when all PRs are merged)

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-74302, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.14.z) matches configured target version for branch (4.14.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-74300 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-74300 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0, 4.15.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.

[openshift-ci-robot]

@dfajmon: Jira Issue OCPBUGS-74302: All pull requests linked via external trackers have merged:

• openshift/kubernetes#2570

This pull request has the verified-later tag and will need to be manually moved to VERIFIED after testing. Jira Issue OCPBUGS-74302 has been moved to the MODIFIED state.

Details

In response to this:

https://issues.redhat.com/browse/OCPBUGS-74302
This test was never used and has been deprecated in versions 4.18 and later.
Continuation of #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:

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.