Skip to content
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

Conformance test setup is flaky (regression) #580

Closed
CecileRobertMichon opened this issue Apr 29, 2020 · 3 comments
Closed

Conformance test setup is flaky (regression) #580

CecileRobertMichon opened this issue Apr 29, 2020 · 3 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@CecileRobertMichon
Copy link
Contributor

CecileRobertMichon commented Apr 29, 2020

/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:

  • I can sometimes repro this locally (but rarely).
  • it seems to be related (time wise) to one of these commits:
    1. 80b6934
    2. ca5226f
    3. eedc11b

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):
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Apr 29, 2020
@CecileRobertMichon
Copy link
Contributor Author

cc @chewong

@CecileRobertMichon CecileRobertMichon changed the title Conformance test setup is flaky Conformance test setup is flaky (regression) Apr 29, 2020
@CecileRobertMichon CecileRobertMichon self-assigned this Apr 29, 2020
@CecileRobertMichon
Copy link
Contributor Author

this has not repro-ed since #581

/close

@k8s-ci-robot
Copy link
Contributor

@CecileRobertMichon: Closing this issue.

In response to this:

this has not repro-ed since #581

/close

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.

Cluster API Azure automation moved this from To do to Done (2020 - Q1) May 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
No open projects
Cluster API Azure
  
Done (2020 - Q1)
Development

No branches or pull requests

2 participants