USHIFT-3315: Increase delete openshift-ingress pod timeout#3439
USHIFT-3315: Increase delete openshift-ingress pod timeout#3439openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@agullon: This pull request references USHIFT-3315 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.17.0" version, but no target version was set. DetailsIn 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. |
| ... Disable Router | ||
|
|
||
| Run With Kubeconfig oc wait --for=delete namespace/openshift-ingress --timeout=60s | ||
| Run With Kubeconfig oc wait --for=delete namespace/openshift-ingress --timeout=300s |
There was a problem hiding this comment.
Can you explain where we need this change? I do not remember this command expiring in MicroShift CI.
There was a problem hiding this comment.
When running RF test suite in QE environment, RF tests execution is stuck in Router Suite Teardown. This is because the pod on openshift-ingress namespace takes more than 60 seconds to be deleted, so teardown process fails and no other RF test is executed. So I tested increasing the timeout and this is issue is no longer reproducible.
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: agullon, ggiguash The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
@agullon: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/cherry-pick release-4.16 |
|
@agullon: new pull request created: #3440 DetailsIn 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 kubernetes-sigs/prow repository. |
4 participants
No description provided.