Description of problem:
[Feature:OpenShiftControllerManager] TestDockercfgTokenDeletedController [Suite:openshift/conformance/parallel]
fail [github.com/onsi/ginkgo/internal/leafnodes/runner.go:113]: timeout: sa1-dockercfg-zdx4x
*** Bug 1765739 has been marked as a duplicate of this bug. ***
confirming the issue is still persistent in e2e tests.
It still exist in e2e test:
*** Bug 1767655 has been marked as a duplicate of this bug. ***
I wonder if this is a watch issue in the test...can we replace the logic in waitForSecretDelete that looks for the deletion event with an explicit poll that simply looks for the secret in question to go missing?
I have just sent a patch that migrates away from watch, let's see if it is an issue there.
The PR that Ricardo mentioned: https://github.com/openshift/origin/pull/24103
[Feature:OpenShiftControllerManager] TestDockercfgTokenDeletedController [Suite:openshift/conformance/parallel] is verified in:
This test failure also occurred in a machine-os-content promotion job https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-promote-openshift-machine-os-content-e2e-aws-4.3/3992
It looks like the fix is supposed to be in, can you please check if the above is the same thing?
Watch has been replaced by Poll, but the test still flakes .
I have this test running individually here for more than 1 hour. It takes less than 10 seconds to complete and I had not even a single failure. Starting to look to see if there may be any problem due to parallel tests.
Moving to 4.4.0, we will likely need to backport to 4.3.0 once we determine the root cause.
*** Bug 1776504 has been marked as a duplicate of this bug. ***
Moving this to 4.3.0 given the impact of this bug.
Still seeing this in recent runs:
(plus many from last night)
This test was (temporarily) disabled as of 15 hours ago:
maybe it hadn't made it through the ART cycle though.
It's disabled only in master (4.4). Do we want to disable it in 4.3?
ugh. yes. thanks Oleg.
Note too that once we uncover the root cause of the flake, we need a 4.3 backport anyway for the .0 release or a z-stream update.
Verified in version:
Reopening. This is likely what is causing the regression in https://bugzilla.redhat.com/show_bug.cgi?id=1785023
Moving back to VERIFIED - fix for regression is being tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1785023
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.