OCPBUGSM-35025: reenable unidling ci tests#27538
OCPBUGSM-35025: reenable unidling ci tests#27538openshift-merge-robot merged 1 commit intoopenshift:masterfrom
Conversation
69e9fc0 to
6900443
Compare
0d85a7d to
85557e5
Compare
85557e5 to
4ba7e18
Compare
|
/lgtm |
|
/retest |
|
/assign @bparees |
|
@dgoodwin what does TRT want to see before this test gets re-enabled? |
|
The fact that this is titled "to debug CI failures" and not "re-enable it because we've fixed it" makes me think this should not merge right now. I'd expect you to either debug the results using CI jobs run against this PR (not merging it until you're satisfied you've fix it), or update the test to always pass but dump out the debugging info you need, if you need more CI runs than you can reasonably get from a single PR, in order to recreate the issue. (The latter should only be done w/ careful tracking of a bug to return the test to properly fail, as well as clear comments in place explaining the situation) |
sorry forget to update the title, I was able to repro the issues manually and was able to verify the fix, we hit the issue with ovn ci runs. |
|
Given it looks like this was originally blocking payloads, we could use the payload command to verify but unfortunately things are not good in master right now for 4.13. With the above details it sounds like we can merge and we will keep an eye out for breakage, if it does we can just revert and go from there. I'll let the team know to watch out for idling test problems on ovn. Naturally we'll want to check all job results and make sure it's not popping up anywhere, including the non-required jobs here. Looks decent from the jobs that completed so far. |
got it, thanks. It looks good to me, but i'm still going to ask @dgoodwin to weigh in in case TRT has any particular concerns or requests before we re-enable. They can remove the hold when they're satisfied. /approve |
|
whoops, race condition w/ Devan. /hold cancel |
|
/retest-required |
4ba7e18 to
6005eeb
Compare
6005eeb to
2dd5e3a
Compare
|
/retest-required |
- idling tests were failing because controller group wasn't matching against the right group. - undiling TCP tests were failing because of curl exit with (7) failed to connect to host error Curling a service with no endpoints has different results: openshift-sdn "hangs" while ovn-k rejects immediately. Because ovk-k refuses the connection curl's retry mechanism doesn't trigger unless --retry-connrefused is specified. Adding it allows the initial curl(s) to fail until the endpoints actually come back from unidling. Signed-off-by: Mohamed Mahmoud <mmahmoud@redhat.com>
2dd5e3a to
b42ae04
Compare
|
/lgtm This test is still disabled both for ovn-k and openshift-sdn: I think we want it enabled at least for ovn-k but @msherif1234 prefers to do that on a different PR. Also, I have seen a flake once but what seems an unrelated reason: Maybe we should follow up anyway. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bparees, jcaamano, msherif1234, oribon 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 |
|
@msherif1234: The following tests failed, say
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/test-infra repository. I understand the commands that are listed here. |
|
Signed-off-by: Mohamed Mahmoud mmahmoud@redhat.com