You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My current guess is that it's 3) somehow but it's hard to prove since it's not 100% reproducible.
Something else I've observed but can't explain yet: this seems to only happen when SKIP_CREATE_CLUSTER is not set, and the cluster is created as part of the test run. This is partly what makes me think 3) might be the culprit.
What did you expect to happen:
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
cluster-api-provider-azure version:
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):
The text was updated successfully, but these errors were encountered:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/kind bug
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
The capz conformance prow job(s)
( definitely seeing it on https://testgrid.k8s.io/provider-azure-periodic#k8s-e2e-conformance-master-capz, haven't observed on https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api-provider-azure#periodic-conformance-v1alpha3 yet but it's possible that it just hasn't hit the issue yet because it runs less frequently).
It seems to fail right after build_k8s() runs. The last line logged before cleanup is
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure
which is the output from
popd
https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/master/scripts/ci-conformance.sh#L67.what I have observed so far:
My current guess is that it's 3) somehow but it's hard to prove since it's not 100% reproducible.
Something else I've observed but can't explain yet: this seems to only happen when SKIP_CREATE_CLUSTER is not set, and the cluster is created as part of the test run. This is partly what makes me think 3) might be the culprit.
What did you expect to happen:
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: