-
Couldn't load subscription status.
- Fork 4.8k
OCPBUGS-63201: Updated the upgrade duration limit to 100 minutes for ppc64le #30390
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.
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
base: main
Are you sure you want to change the base?
Conversation
|
@KeerthanaAP: This pull request references Jira Issue OCPBUGS-63201, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this: 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. |
|
/jira refresh |
|
@KeerthanaAP: This pull request references Jira Issue OCPBUGS-63201, which is invalid:
Comment In response to this:
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. |
|
/jira refresh |
|
@KeerthanaAP: This pull request references Jira Issue OCPBUGS-63201, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
In response to this:
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. |
|
/retest |
|
/test go-verify-deps |
d3939b2 to
51e231d
Compare
|
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: 51e231d
New tests seen in this PR at sha: 51e231d
|
51e231d to
6950dd9
Compare
|
Risk analysis has seen new tests most likely introduced by this PR. New tests seen in this PR at sha: 6950dd9
|
|
/test okd-scos-e2e-aws-ovn |
|
/lgtm |
|
/lgtm |
|
@KeerthanaAP: The following test failed, say
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. |
|
Why is raising the limit the correct action here? Neither the description here or the linked OCPBUGS card tells whether there was some investigation made. Can we rule out the possibility that the product really got worse? |
|
@KeerthanaAP: This pull request references Jira Issue OCPBUGS-63201, which is valid. 3 validation(s) were run on this bug
In response to this:
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. |
|
@petr-muller As mentioned in the OpenShift bug report, recent upgrades have been taking longer than 80 minutes. To address this, we are increasing the timeout to 100 minutes. We are continuing to investigate the underlying network or compute issues causing the delay, and once the problem is resolved, the timeout will be reverted to 80 minutes. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: KeerthanaAP, neisw, prb112, tvardema 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 |
|
/verified later @KeerthanaAP |
|
@KeerthanaAP: This PR has been marked to be verified later by In response to this:
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. |
As the upgrade in ppc64le took more than 80 mins in recent runs, Updating the duration limit to 100minutes as a workaround.