-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.19.z
-
None
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The stated test:
https://github.com/openshift/machine-config-operator/blob/release-4.19/test/e2e/mcn_test.go#L16
It has flakes at least 3 times in recent (2 months) runs on 4.19:
https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_machine-config-operator/5300/pull-ci-openshift-machine-config-operator-release-4.19-e2e-gcp-op/1970493026836942848
https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_machine-config-operator/5324/pull-ci-openshift-machine-config-operator-release-4.19-e2e-gcp-op/1978178250190360576
https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_machine-config-operator/5324/pull-ci-openshift-machine-config-operator-release-4.19-e2e-gcp-op/1976490625763119104
With the following error signature:
=== RUN TestMCNScopeSadPath
mcn_test.go:28:
Error Trace: /go/src/github.com/openshift/machine-config-operator/test/e2e/mcn_test.go:28
Error: "Error from server: error dialing backend: dial tcp 10.0.128.3:10250: connect: connection refused\n" does not contain "updates to MCN ci-op-xhrct6yq-5691c-qbbwm-master-1 can only be done from the MCN's owner node"
Test: TestMCNScopeSadPath
10250 is well known kubelet port kubelet.
Version-Release number of selected component (if applicable):
Seen on 4.19 but maybe on other versions.
How reproducible:
Unsure - on 4.19, I see it 1 out of every 10 runs rought.
Steps to Reproduce:
1. Run the CI
2.
3.
Actual results:
Expected results:
Additional info:
I also see e2e: TestMCNScopeHappyPath fail with a similiar error signature. Â
