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.

Sign up for GitHub

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

Jump to bottom

capi-e2e MachinePools test is failing #4205

Closed
fabriziopandini opened this issue Feb 18, 2021 · 5 comments · Fixed by #4208
Closed

capi-e2e MachinePools test is failing #4205

fabriziopandini opened this issue Feb 18, 2021 · 5 comments · Fixed by #4208
Assignees
@sedefsavas
Labels
area/testing Issues or PRs related to testing help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v0.4

Comments

@fabriziopandini
Copy link
Member

See https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api#capi-e2e-main

capi-e2e.When testing MachinePools is failing while waiting for the cluster to be provisioned

INFO: Waiting for the cluster infrastructure to be provisioned
STEP: Waiting for cluster to enter the provisioned phase
INFO: Waiting for control plane to be initialized
INFO: Waiting for the first control plane machine managed by machine-pool-cc8ln5/machine-pool-1mm5fa-control-plane to be provisioned
STEP: Waiting for one control plane node to exist
INFO: Waiting for control plane to be ready
INFO: Waiting for control plane machine-pool-cc8ln5/machine-pool-1mm5fa-control-plane to be ready (implies underlying nodes to be ready as well)
STEP: Waiting for the control plane to be ready
INFO: Waiting for the machine deployments to be provisioned
INFO: Waiting for the machine pools to be provisioned
STEP: Waiting for the machine pool workload nodes to exist


• Failure [1033.699 seconds]
When testing MachinePools [Periodic-K8SVersion]
/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/machine_pool_test.go:27
  Should successfully create a cluster with machine pool machines [It]
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/machine_pool.go:72
  Timed out after 900.000s.
  Expected
      <int>: 0
  to equal
      <int>: 2
  /home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/machinepool_helpers.go:85
  Full Stack Trace
  sigs.k8s.io/cluster-api/test/framework.WaitForMachinePoolNodesToExist(0x1f0c7e0, 0xc000124018, 0x7fc959ec6d98, 0xc0001f8000, 0xc0000eac00, 0x0, 0x0, 0x0)
  	/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/machinepool_helpers.go:85 +0x4a7
  sigs.k8s.io/cluster-api/test/framework.DiscoveryAndWaitForMachinePools(0x1f0c7e0, 0xc000124018, 0x7fc959ec6d98, 0xc0001f8000, 0x7fc959f22ac0, 0xc0007620e0, 0xc00068c4e0, 0x0, 0x0, 0x0, ...)
  	/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/machinepool_helpers.go:107 +0x4b2
  sigs.k8s.io/cluster-api/test/framework/clusterctl.ApplyClusterTemplateAndWait(0x1f0c7e0, 0xc000124018, 0x1f24a80, 0xc00044d700, 0xc000ab40c0, 0x22, 0xc00044e0f6, 0x31, 0xc00044e128, 0x16, ...)
  	/home/prow/go/src/sigs.k8s.io/cluster-api/test/framework/clusterctl/clusterctl_helpers.go:195 +0x126c
  sigs.k8s.io/cluster-api/test/e2e.MachinePoolSpec.func2()
  	/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/machine_pool.go:75 +0x665
  github.com/onsi/ginkgo/internal/leafnodes.(*runner).runSync(0xc0001ffe60, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
  	/home/prow/go/pkg/mod/github.com/onsi/[email protected]/internal/leafnodes/runner.go:113 +0xa3
  github.com/onsi/ginkgo/internal/leafnodes.(*runner).run(0xc0001ffe60, 0x3, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
  	/home/prow/go/pkg/mod/github.com/onsi/[email protected]/internal/leafnodes/runner.go:64 +0xd7
  github.com/onsi/ginkgo/internal/leafnodes.(*ItNode).Run(0xc000268d80, 0x1ec7200, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
  	/home/prow/go/pkg/mod/github.com/onsi/[email protected]/internal/leafnodes/it_node.go:26 +0x67
  github.com/onsi/ginkgo/internal/spec.(*Spec).runSample(0xc0004923c0, 0x0, 0x1ec7200, 0xc00015c8c0)
  	/home/prow/go/pkg/mod/github.com/onsi/[email protected]/internal/spec/spec.go:215 +0x691
  github.com/onsi/ginkgo/internal/spec.(*Spec).Run(0xc0004923c0, 0x1ec7200, 0xc00015c8c0)
  	/home/prow/go/pkg/mod/github.com/onsi/[email protected]/internal/spec/spec.go:138 +0xf2
  github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).runSpec(0xc0005b6000, 0xc0004923c0, 0x1)
  	/home/prow/go/pkg/mod/github.com/onsi/[email protected]/internal/specrunner/spec_runner.go:200 +0x111
  github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).runSpecs(0xc0005b6000, 0x1)
  	/home/prow/go/pkg/mod/github.com/onsi/[email protected]/internal/specrunner/spec_runner.go:170 +0x127
  github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).Run(0xc0005b6000, 0xc0000420a0)
  	/home/prow/go/pkg/mod/github.com/onsi/[email protected]/internal/specrunner/spec_runner.go:66 +0x117
  github.com/onsi/ginkgo/internal/suite.(*Suite).Run(0xc000178070, 0x7fc959f5b328, 0xc000603080, 0x1c8da39, 0x8, 0xc000268480, 0x2, 0x2, 0x1f15460, 0xc00015c8c0, ...)
  	/home/prow/go/pkg/mod/github.com/onsi/[email protected]/internal/suite/suite.go:79 +0x586
  github.com/onsi/ginkgo.RunSpecsWithCustomReporters(0x1ec88e0, 0xc000603080, 0x1c8da39, 0x8, 0xc000268460, 0x2, 0x2, 0x2)
  	/home/prow/go/pkg/mod/github.com/onsi/[email protected]/ginkgo_dsl.go:219 +0x238
  github.com/onsi/ginkgo.RunSpecsWithDefaultAndCustomReporters(0x1ec88e0, 0xc000603080, 0x1c8da39, 0x8, 0xc000078f60, 0x1, 0x1, 0x602e6aa9)
  	/home/prow/go/pkg/mod/github.com/onsi/[email protected]/ginkgo_dsl.go:207 +0xad
  sigs.k8s.io/cluster-api/test/e2e.TestE2E(0xc000603080)
  	/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/e2e_suite_test.go:86 +0x136
  testing.tRunner(0xc000603080, 0x1d5dd28)
  	/usr/local/go/src/testing/testing.go:1123 +0xef
  created by testing.(*T).Run
  	/usr/local/go/src/testing/testing.go:1168 +0x2b3

/kind flake
@k8s-ci-robot k8s-ci-robot added the kind/flake Categorizes issue or PR as related to a flaky test. label Feb 18, 2021
@fabriziopandini
Copy link
Member Author

/area testing
/priority important soon
/milestone v0.4.0

/help

@k8s-ci-robot
Copy link
Contributor

@fabriziopandini:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/area testing
/priority important soon
/milestone v0.4.0

/help

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.

@k8s-ci-robot
Copy link
Contributor

@fabriziopandini: The label(s) priority/important, priority/soon cannot be applied, because the repository doesn't have them

In response to this:

/area testing
/priority important soon
/milestone v0.4.0

/help

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.

@k8s-ci-robot k8s-ci-robot added this to the v0.4.0 milestone Feb 18, 2021
@k8s-ci-robot k8s-ci-robot added area/testing Issues or PRs related to testing help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Feb 18, 2021
@fabriziopandini fabriziopandini added kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed kind/flake Categorizes issue or PR as related to a flaky test. labels Feb 18, 2021
@vincepri
Copy link
Member

@shysank @sedefsavas Would you be able to debug this issue?

@sedefsavas
Copy link

Yes, I will take a look.
/assign

@sedefsavas sedefsavas mentioned this issue Feb 19, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sedefsavas sedefsavas

Labels
area/testing Issues or PRs related to testing help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v0.4
Development

Successfully merging a pull request may close this issue.

🐛 Fix docker machine pool status update sedefsavas/cluster-api
4 participants
@vincepri @fabriziopandini @k8s-ci-robot @sedefsavas