cluster-api-provider-aws: Test failure: capa-conformance-stable*
Recent failures:
- https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-cluster-api-provider-aws-make-conformance-stable/1202280071990087680
- https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-cluster-api-provider-aws-make-conformance-stable-k8s-ci-artifacts/1202280072006864896
Both seem to have similar errors:
I1204 17:58:17.890103 14265 clusterclient.go:242] Waiting to acquire client... server not yet available: Get https://test1-apiserver-724810617.us-west-2.elb.amazonaws.com:6443/api?timeout=32s: EOF
F1204 17:58:17.890447 14265 alpha_phase_apply_addons.go:51] unable to create cluster client: failed to acquire new client: timed out waiting for the condition
make: *** [Makefile:328: create-cluster-management] Error 1
We have an issue where we are currently unable to retrieve log files from the VMs. I have opened #1388 to try to address this, to assist with debugging.
/assign /lifecycle active /kind failing-test /priority critical-urgent /milestone v0.5.0
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 19 (19 by maintainers)
I think I’m going to have to try to run this locally to see if I can reproduce. For some reason gathering logs is not seeing the first control plane VM, which is what we need to determine why the apiserver isn’t coming online.