Skip to content

Conversation

@RishabhSaini
Copy link
Contributor

helpers: vSphere 2x upload is time consuming hence bump timeout

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 22, 2025
@RishabhSaini RishabhSaini changed the title Bump timeout for vSphereBootimageUpdate tests MCO-1875: Bump timeout for vSphereBootimageUpdate tests Sep 22, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 22, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 22, 2025

@RishabhSaini: This pull request references MCO-1875 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.21.0" version, but no target version was set.

In response to this:

helpers: vSphere 2x upload is time consuming hence bump timeout

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.

@djoshy
Copy link
Contributor

djoshy commented Sep 22, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 22, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: djoshy, RishabhSaini

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

@yuqi-zhang
Copy link
Contributor

Since this is a timeout bump, probably best verified via followup CI runs.

/verified later @RishabhSaini

@openshift-ci-robot openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Sep 23, 2025
@openshift-ci-robot
Copy link

@yuqi-zhang: This PR has been marked to be verified later by @RishabhSaini.

In response to this:

Since this is a timeout bump, probably best verified via followup CI runs.

/verified later @RishabhSaini

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

/retest-required

Remaining retests: 0 against base HEAD 92f0f58 and 2 for PR HEAD a2c9b7f in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a08d2f3 and 1 for PR HEAD a2c9b7f in total

@RishabhSaini
Copy link
Contributor Author

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6d8c2d0 and 0 for PR HEAD a2c9b7f in total

@openshift-ci-robot
Copy link

/hold

Revision a2c9b7f was retested 3 times: holding

@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 Sep 25, 2025
@RishabhSaini
Copy link
Contributor Author

/unhold

@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 Sep 26, 2025
@RishabhSaini
Copy link
Contributor Author

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 506d6c4 and 2 for PR HEAD a2c9b7f in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 27, 2025

@RishabhSaini: 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 a2c9b7f link false /test e2e-aws-ovn
ci/prow/e2e-aws-ovn-upgrade a2c9b7f link false /test e2e-aws-ovn-upgrade
ci/prow/e2e-metal-ipi-ovn a2c9b7f link false /test e2e-metal-ipi-ovn
ci/prow/e2e-aws-ovn-single-node-serial a2c9b7f link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-ovn-cgroupsv2 a2c9b7f link false /test e2e-aws-ovn-cgroupsv2
ci/prow/okd-scos-e2e-aws-ovn a2c9b7f link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-single-node-upgrade a2c9b7f link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-azure a2c9b7f link false /test e2e-azure
ci/prow/e2e-agnostic-ovn-cmd a2c9b7f link false /test e2e-agnostic-ovn-cmd
ci/prow/e2e-metal-ipi-virtualmedia a2c9b7f link false /test e2e-metal-ipi-virtualmedia
ci/prow/e2e-aws-ovn-edge-zones a2c9b7f link false /test e2e-aws-ovn-edge-zones
ci/prow/e2e-openstack-ovn a2c9b7f link false /test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-kube-apiserver-rollout a2c9b7f link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-single-node a2c9b7f link false /test e2e-aws-ovn-single-node
ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway a2c9b7f link false /test e2e-metal-ipi-ovn-dualstack-local-gateway
ci/prow/e2e-aws-proxy a2c9b7f link false /test e2e-aws-proxy
ci/prow/e2e-aws-disruptive a2c9b7f link false /test e2e-aws-disruptive
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout a2c9b7f link false /test e2e-metal-ipi-ovn-kube-apiserver-rollout

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

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 44be851 and 1 for PR HEAD a2c9b7f in total

@openshift-merge-bot openshift-merge-bot bot merged commit 6079513 into openshift:main Sep 27, 2025
29 of 47 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria verified-later

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants