Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[release-4.14] UPSTREAM: 120961: e2e: bootstrap vsphere tests earlier #1730

Open
wants to merge 1 commit into
base: release-4.14
Choose a base branch
from
Open

[release-4.14] UPSTREAM: 120961: e2e: bootstrap vsphere tests earlier #1730

wants to merge 1 commit into from

Conversation

mkowalski
Copy link

This is a manual cherry-pick of #1714

@openshift-ci-robot openshift-ci-robot added the backports/validated-commits Indicates that all commits come to merged upstream PRs. label Oct 2, 2023
@openshift-ci-robot
Copy link

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

The following commits are valid:

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

@mkowalski
Copy link
Author

/test e2e-vsphere

@openshift-ci openshift-ci bot requested review from mfojtik and soltysh October 2, 2023 08:43
@mkowalski
Copy link
Author

/cc @bertinatto

@openshift-ci openshift-ci bot requested a review from bertinatto October 2, 2023 08:44
@mkowalski mkowalski mentioned this pull request Oct 2, 2023
Merged
@openshift-ci-robot openshift-ci-robot added backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. and removed backports/validated-commits Indicates that all commits come to merged upstream PRs. labels Oct 2, 2023
@openshift-ci-robot
Copy link

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

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

@mkowalski
Copy link
Author

/retitle [release-4.14] UPSTREAM: 120961: e2e: bootstrap vsphere tests earlier

@openshift-ci openshift-ci bot changed the title [release-4.14] UPSTREAM: 120817: e2e: bootstrap vsphere tests earlier [release-4.14] UPSTREAM: 120961: e2e: bootstrap vsphere tests earlier Oct 2, 2023
@mkowalski
Copy link
Author

/test unit

Blind retest, don't understand the failure

@mkowalski
Copy link
Author

/test ?

@openshift-ci
Copy link

openshift-ci bot commented Oct 2, 2023

@mkowalski: The following commands are available to trigger required jobs:

  • /test artifacts
  • /test configmap-scale
  • /test e2e-aws-crun-wasm
  • /test e2e-aws-jenkins
  • /test e2e-aws-ovn-cgroupsv2
  • /test e2e-aws-ovn-crun
  • /test e2e-aws-ovn-downgrade
  • /test e2e-aws-ovn-fips
  • /test e2e-aws-ovn-serial
  • /test e2e-aws-ovn-upgrade
  • /test e2e-azure-ovn-upgrade
  • /test e2e-gcp
  • /test e2e-gcp-ovn-upgrade
  • /test images
  • /test integration
  • /test k8s-e2e-conformance-aws
  • /test k8s-e2e-gcp-ovn
  • /test k8s-e2e-gcp-serial
  • /test unit
  • /test verify
  • /test verify-commits

The following commands are available to trigger optional jobs:

  • /test e2e-agnostic-ovn-cmd
  • /test e2e-aws
  • /test e2e-aws-csi
  • /test e2e-aws-disruptive
  • /test e2e-aws-multitenant
  • /test e2e-aws-ovn
  • /test e2e-aws-single-node
  • /test e2e-azure
  • /test e2e-metal-ipi
  • /test e2e-metal-ipi-ovn-dualstack
  • /test e2e-metal-ipi-ovn-ipv6
  • /test e2e-openstack
  • /test e2e-openstack-csi-cinder
  • /test e2e-openstack-csi-manila
  • /test e2e-vsphere
  • /test k8s-e2e-aws
  • /test k8s-e2e-aws-ovn-serial
  • /test k8s-e2e-gcp-five-control-plane-replicas

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-kubernetes-release-4.14-e2e-agnostic-ovn-cmd
  • pull-ci-openshift-kubernetes-release-4.14-e2e-aws-crun-wasm
  • pull-ci-openshift-kubernetes-release-4.14-e2e-aws-csi
  • pull-ci-openshift-kubernetes-release-4.14-e2e-aws-ovn-cgroupsv2
  • pull-ci-openshift-kubernetes-release-4.14-e2e-aws-ovn-crun
  • pull-ci-openshift-kubernetes-release-4.14-e2e-aws-ovn-fips
  • pull-ci-openshift-kubernetes-release-4.14-e2e-aws-ovn-serial
  • pull-ci-openshift-kubernetes-release-4.14-e2e-gcp
  • pull-ci-openshift-kubernetes-release-4.14-e2e-gcp-ovn-upgrade
  • pull-ci-openshift-kubernetes-release-4.14-images
  • pull-ci-openshift-kubernetes-release-4.14-integration
  • pull-ci-openshift-kubernetes-release-4.14-k8s-e2e-aws-ovn-serial
  • pull-ci-openshift-kubernetes-release-4.14-k8s-e2e-conformance-aws
  • pull-ci-openshift-kubernetes-release-4.14-k8s-e2e-gcp-ovn
  • pull-ci-openshift-kubernetes-release-4.14-k8s-e2e-gcp-serial
  • pull-ci-openshift-kubernetes-release-4.14-unit
  • pull-ci-openshift-kubernetes-release-4.14-verify
  • pull-ci-openshift-kubernetes-release-4.14-verify-commits

In response to this:

/test ?

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.

@mkowalski
Copy link
Author

/test e2e-vsphere

@mkowalski
Copy link
Author

/validate-backports

@openshift-ci-robot
Copy link

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

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

@bertinatto
Copy link
Member

/lgtm

/hold
for e2e-vspher

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 2, 2023
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 2, 2023
soltysh
soltysh approved these changes Oct 2, 2023
View reviewed changes
Copy link
Member

@soltysh soltysh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/remove-label backports/unvalidated-commits
/label backports/validated-commits
/approve
/label backport-risk-assessed

@openshift-ci openshift-ci bot added backports/validated-commits Indicates that all commits come to merged upstream PRs. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. and removed backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. labels Oct 2, 2023
@soltysh
Copy link
Member

soltysh commented Oct 2, 2023

/retest-required

@openshift-ci
Copy link

openshift-ci bot commented Oct 2, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto, mkowalski, soltysh

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

The pull request process is described here

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 2, 2023
@mkowalski
Copy link
Author

/test e2e-vsphere

It panicked the hard way... Maybe we need kubernetes#120950 too, don't know yet

@mkowalski
Copy link
Author

/test unit

@miyadav
Copy link
Member

miyadav commented Oct 3, 2023 •
edited

/label cherry-pick-approved

Based on pre-merge test.

@openshift-ci
Copy link

openshift-ci bot commented Oct 3, 2023

@miyadav: Can not set label cherry-pick-approved: Must be member in one of these teams: []

In response to this:

/label cherry-pick-approved

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.

@bertinatto
Copy link
Member

/test unit

@soltysh
Copy link
Member

soltysh commented Oct 3, 2023

/hold cancel
/override ci/prow/e2e-aws-ovn-fips

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 3, 2023
@openshift-ci
Copy link

openshift-ci bot commented Oct 3, 2023

@soltysh: Overrode contexts on behalf of soltysh: ci/prow/e2e-aws-ovn-fips

In response to this:

/hold cancel
/override ci/prow/e2e-aws-ovn-fips

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.

@bertinatto
Copy link
Member

/test unit

1 similar comment
@bertinatto
Copy link
Member

/test unit

@openshift-merge-robot
Copy link

@mkowalski: 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-crun-wasm d6210ad link true /test e2e-aws-crun-wasm
ci/prow/e2e-aws-ovn-fips d6210ad link true /test e2e-aws-ovn-fips
ci/prow/unit d6210ad link true /test unit

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.

@bertinatto
Copy link
Member

/retest

@bertinatto
Copy link
Member

/test unit

@openshift-ci
Copy link

openshift-ci bot commented Oct 5, 2023

@mkowalski: 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-fips d6210ad link true /test e2e-aws-ovn-fips
ci/prow/e2e-aws-crun-wasm d6210ad link true /test e2e-aws-crun-wasm

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
Copy link

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-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 4, 2024
@mkowalski
Copy link
Author

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 4, 2024
@openshift-bot
Copy link

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-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 3, 2024
@mkowalski
Copy link
Author

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@soltysh soltysh soltysh approved these changes

@mfojtik mfojtik Awaiting requested review from mfojtik

@bertinatto bertinatto Awaiting requested review from bertinatto

Assignees

@bertinatto bertinatto

@kasturinarra kasturinarra

@zhouying7780 zhouying7780

@xingxingxia xingxingxia

@sunilcio sunilcio

@duanwei33 duanwei33

@wangke19 wangke19

@gangwgr gangwgr

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. backports/validated-commits Indicates that all commits come to merged upstream PRs. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet