Skip to content

Comments

increase gcp-ovn-rt-upgrade timeout from 5h->6h#69287

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
jluhrsen:increase-gcp-ovn-rt-upgrade-timeout
Oct 16, 2025
Merged

increase gcp-ovn-rt-upgrade timeout from 5h->6h#69287
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
jluhrsen:increase-gcp-ovn-rt-upgrade-timeout

Conversation

@jluhrsen
Copy link
Contributor

it some times will go past 5h and fails, even though its working on post steps and the actual e2e part has passed

@martinkennelly
Copy link
Contributor

can you run the job a few times here so we can see the effect of your changes and see if it passes?

@jluhrsen
Copy link
Contributor Author

/pj-reherse pull-ci-openshift-ovn-kubernetes-master-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade

1 similar comment
@martinkennelly
Copy link
Contributor

/pj-reherse pull-ci-openshift-ovn-kubernetes-master-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade

@martinkennelly
Copy link
Contributor

doesnt seem to be working jamo

@martinkennelly
Copy link
Contributor

/pj-rehearse pull-ci-openshift-ovn-kubernetes-master-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade

@openshift-ci-robot
Copy link
Contributor

@martinkennelly: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@jluhrsen
Copy link
Contributor Author

doesnt seem to be working jamo

it's working now. pj-rehearse likes to ignore you sometimes. :(

but I think we should
/hold
now that I realize the periodic job is also facing this same issue in the past month. this is something bigger that someone probably needs to look in to. I mean, we can merge this if we want, but I did start a discussion on slack to see if others
know about this and maybe someone is working on it.

@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 23, 2025
@martinkennelly
Copy link
Contributor

we can abandon this jamo i think - we saw something in the logs: https://redhat-internal.slack.com/archives/C01CQA76KMX/p1758716716570649?thread_ts=1758647063.563739&cid=C01CQA76KMX

@jluhrsen
Copy link
Contributor Author

we can abandon this jamo i think - we saw something in the logs: https://redhat-internal.slack.com/archives/C01CQA76KMX/p1758716716570649?thread_ts=1758647063.563739&cid=C01CQA76KMX

/close

@openshift-ci openshift-ci bot closed this Sep 24, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 24, 2025

@jluhrsen: Closed this PR.

Details

In response to this:

we can abandon this jamo i think - we saw something in the logs: https://redhat-internal.slack.com/archives/C01CQA76KMX/p1758716716570649?thread_ts=1758647063.563739&cid=C01CQA76KMX

/close

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.

@martinkennelly
Copy link
Contributor

/reopen

@openshift-ci openshift-ci bot reopened this Oct 10, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 10, 2025

@martinkennelly: Reopened this PR.

Details

In response to this:

/reopen

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 openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 10, 2025
@martinkennelly
Copy link
Contributor

martinkennelly commented Oct 10, 2025

@jluhrsen I looked at this job and i think your instincts/analysis were right originally... it does look at the job and it passes the tests after 3 hours but then hits the timeout sometimes. I dont see any other issues.... so it does just look like things are just taking longer and then timing out...

@martinkennelly
Copy link
Contributor

/pj-rehearse pull-ci-openshift-ovn-kubernetes-master-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade

@openshift-ci-robot
Copy link
Contributor

@martinkennelly: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot
Copy link
Contributor

@martinkennelly: job(s): pull-ci-openshift-ovn-kubernetes-master-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade either don't exist or were not found to be affected, and cannot be rehearsed

@jluhrsen
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-ovn-kubernetes-master-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade

@openshift-ci-robot
Copy link
Contributor

@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@jluhrsen
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-ovn-kubernetes-master-4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-rt-upgrade

@openshift-ci-robot
Copy link
Contributor

@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@martinkennelly
Copy link
Contributor

/lgtm
/approve

TYSM jamo..

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

@jluhrsen can you give your reasoning for including the job openshift-upgrade-aws-single-node-realtime ?

@jluhrsen jluhrsen force-pushed the increase-gcp-ovn-rt-upgrade-timeout branch from 44708b8 to 70b5881 Compare October 16, 2025 19:22
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 16, 2025
@jluhrsen
Copy link
Contributor Author

single-node-realtime

@martinkennelly , I have fat fingers I guess. unintentional. fixed. need the labels back pls

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 16, 2025

@jluhrsen: 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/rehearse/openshift/ovn-kubernetes/master/4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade f2517de link unknown /pj-rehearse pull-ci-openshift-ovn-kubernetes-master-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade

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.

@martinkennelly
Copy link
Contributor

@jluhrsen generated config job isn't happy.

@martinkennelly
Copy link
Contributor

/hold

until generated config is good

it some times will go past 5h and fails, even though its
working on post steps and the actual e2e part has passed

on major factor for these specific jobs is that the build
time for OVNK presubmits can take 30-60+ minutes just to
build the PR before the job can even start the process of
starting a cluster to run the e2e.

Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
@jluhrsen jluhrsen force-pushed the increase-gcp-ovn-rt-upgrade-timeout branch from 70b5881 to 6b120d9 Compare October 16, 2025 20:41
@jluhrsen
Copy link
Contributor Author

/hold

until generated config is good

@martinkennelly should be good now. forgot to run the make commands after fixing the last fat figure mistake

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 16, 2025
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@jluhrsen: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-ovn-kubernetes-master-4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-rt-upgrade openshift/ovn-kubernetes presubmit Ci-operator config changed
pull-ci-openshift-ovn-kubernetes-release-4.18-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade openshift/ovn-kubernetes presubmit Ci-operator config changed
pull-ci-openshift-ovn-kubernetes-release-4.20-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade openshift/ovn-kubernetes presubmit Ci-operator config changed
pull-ci-openshift-ovn-kubernetes-release-4.19-4.19-upgrade-from-stable-4.18-e2e-gcp-ovn-rt-upgrade openshift/ovn-kubernetes presubmit Ci-operator config changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@martinkennelly
Copy link
Contributor

/lgtm

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

openshift-ci bot commented Oct 16, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jluhrsen, martinkennelly

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:

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

@martinkennelly
Copy link
Contributor

martinkennelly commented Oct 16, 2025

/rehearsals-ack

@martinkennelly
Copy link
Contributor

/rehearse ack

@martinkennelly
Copy link
Contributor

@jluhrsen can you ack rehearsals? We've already verified it.

@martinkennelly
Copy link
Contributor

/pj-rehearse ack

@openshift-ci-robot
Copy link
Contributor

@martinkennelly: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Oct 16, 2025
@martinkennelly
Copy link
Contributor

/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 Oct 16, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit e63e209 into openshift:master Oct 16, 2025
15 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. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants