Bug 1789746: Ensure enough number of retries for cluster with Kuryr SDN #2899
Conversation
When using Kuryr SDN the number of resources created on the OpenStack side is way larger than for the OpenShift SDN case. For this reason, as there is no specific order for the resources to be deleted, the chances of the deletion of one resource (e.g., a network) being blocked by the deletion of another (e.g. a port on that network) are higher, thus needed more retries.
openshift-ci-robot
added
the
size/XS
|
/assign @mandre |
luis5tb
changed the title
|
@luis5tb: This pull request references Bugzilla bug 1789746, which is valid. The bug has been moved to the POST state. 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 kubernetes/test-infra repository. |
openshift-ci-robot
added
the
bugzilla/valid-bug
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mandre 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 |
openshift-ci-robot
added
the
approved
|
/test e2e-libvirt |
|
/retest |
1 similar comment
|
/retest |
|
/uncc @jstuever |
openshift-ci-robot
requested review from
tomassedovic
and removed request for
jstuever
|
/retest |
|
woops, I got the math wrong :) that should be a bit over 2 hours, which I guess is acceptable even for the CI. 👍 |
|
/lgtm |
|
/test e2e-libvirt |
|
/hold Feel free to |
openshift-ci-robot
added
the
do-not-merge/hold
|
/test e2e-libvirt |
|
/lgtm |
openshift-ci-robot
removed
the
do-not-merge/hold
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@luis5tb: All pull requests linked via external trackers have merged. Bugzilla bug 1789746 has been moved to the MODIFIED state. 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 kubernetes/test-infra repository. |
|
@luis5tb: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
|
/cherry-pick release-4.3 |
|
@luis5tb: new pull request created: #2903 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 kubernetes/test-infra repository. |
When using Kuryr SDN the number of resources created on the
OpenStack side is way larger than for the OpenShift SDN case.
For this reason, as there is no specific order for the resources
to be deleted, the chances of the deletion of one resource (e.g.,
a network) being blocked by the deletion of another (e.g. a port
on that network) are higher, thus needed more retries.