https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/22455/pull-ci-openshift-origin-master-unit/4554#githubcomopenshiftoriginvendork8siokubernetespkgkubeletcmdevicemanager-testnewmanagerimplstartprobemode === RUN TestNewManagerImplStartProbeMode 2019/04 ... === RUN TestNewManagerImplStartProbeMode 2019/04/02 19:35:19 Starting to serve on /tmp/volume/device_plugin355861278/device-plugin.sock E0402 19:35:19.844615 13396 plugin_watcher.go:120] error stat file /tmp/volume/device_plugin355861278/device-plugin.sock failed: stat /tmp/volume/device_plugin355861278/device-plugin.sock: no such file or directory when handling create event: "/tmp/volume/device_plugin355861278/device-plugin.sock": CREATE --- FAIL: TestNewManagerImplStartProbeMode (11.01s) assertions.go:254: Error Trace: manager_test.go:275 manager_test.go:81 Error: Received unexpected error: timeout on stopping watcher Test: TestNewManagerImplStartProbeMode Failing very frequently post rebase
fabio has a fix upstream being reviewed: https://github.com/kubernetes/kubernetes/pull/75110. upstream issue: https://github.com/kubernetes/kubernetes/issues/75097 I tested the fix locally and it doesn't seem to solve the problem totally, the test still fails frequently. I also tried testing it in combination with https://github.com/openshift/origin/pull/22055 and the test still fails.
correction, we already have 22055 from the rebase so my patch did nothing. Will defer to fabio for progress on https://github.com/kubernetes/kubernetes/pull/75110
This is still failing and blocking the origin queue. Moving back to 4.1.0
Moving this back to high because I'm disabling it because we couldn't get a fix in time https://github.com/openshift/origin/pull/22527 This will come back with the next rebase so leaving it on high.
*** Bug 1698538 has been marked as a duplicate of this bug. ***
OpenShift patch merged: https://github.com/openshift/origin/pull/22715
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days