-
Notifications
You must be signed in to change notification settings - Fork 39.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TestNamespaceController {namespace} #33838
Comments
GetObjectFromChan() is timing out (20s) and returning nil causing the panic. Happens in TestSecretController (and probably TestIngressController) controller as well. |
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-test-go/17636/ Failed: TestNamespaceController {namespace}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-test-go/17646/ Failed: TestNamespaceController {namespace}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-test-go/17653/ Failed: TestNamespaceController {namespace}
|
[FLAKE-PING] @apelisse This flaky-test issue would love to have more attention. |
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-test-go/17670/ Failed: TestNamespaceController {namespace}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-test-go/17673/ Failed: TestNamespaceController {namespace}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-test-go/17676/ Failed: TestNamespaceController {namespace}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-test-go/17689/ Failed: TestNamespaceController {namespace}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-test-go/17697/ Failed: TestNamespaceController {namespace}
|
/cc OWNERS of |
I think this is also related to Issue #33880. |
fix is pending #33866 |
Automatic merge from submit-queue wait for federation informer store to catch up before update Fixes #33838 #33880 There is a flake in the federation-controller code where an update to a resource is done too quickly after the create. Because the resource is not yet in the federated informer store, when the reconcile<Resource>() is called, it can't find the resource and treats the change as a create rather than a update. This causes a failure (actually a panic) in the test code, which expects an update event, not a create, in response to the resource modification. @derekwaynecarr @apelisse @mwielgus
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-test-go/17573/
Failed: TestNamespaceController {namespace}
Previous issues for this test: #30855
The text was updated successfully, but these errors were encountered: