This job view page is being replaced by Spyglass soon. Check out the new job view.
PRsedefsavas: Bump Kubernetes to v1.24.0 and fix AWSMachinePool minsize
ResultFAILURE
Tests 1 failed / 23 succeeded
Started2022-07-14 20:44
Elapsed2h8m
Revision3083dd4f85383b3e656f2fa259697fe82a2c4ec6
Refs 3468

Test Failures


capa-e2e [unmanaged] [Cluster API Framework] Machine Pool Spec Should successfully create a cluster with machine pool machines 1h14m

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capa\-e2e\s\[unmanaged\]\s\[Cluster\sAPI\sFramework\]\sMachine\sPool\sSpec\sShould\ssuccessfully\screate\sa\scluster\swith\smachine\spool\smachines$'
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/machine_pool.go:76
Timed out after 2400.001s.
Expected
    <int>: 1
to equal
    <int>: 0
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/framework/machinepool_helpers.go:90
				
				Click to see stdout/stderrfrom junit.e2e_suite.7.xml

Filter through log files | View test history on testgrid


Show 23 Passed Tests

Show 4 Skipped Tests

Error lines from build-log.txt

... skipping 466 lines ...
[1]  ✓ Installing CNI 🔌
[1]  • Installing StorageClass 💾  ...
[1]  ✓ Installing StorageClass 💾
[1] INFO: The kubeconfig file for the kind cluster is /tmp/e2e-kind3769690983
[1] INFO: Loading image: "gcr.io/k8s-staging-cluster-api/capa-manager:e2e"
[1] INFO: Loading image: "quay.io/jetstack/cert-manager-cainjector:v1.7.2"
[1] INFO: [WARNING] Unable to load image "quay.io/jetstack/cert-manager-cainjector:v1.7.2" into the kind cluster "test-lir5iz": error saving image "quay.io/jetstack/cert-manager-cainjector:v1.7.2" to "/tmp/image-tar3597219410/image.tar": unable to read image data: Error response from daemon: reference does not exist
[1] INFO: Loading image: "quay.io/jetstack/cert-manager-webhook:v1.7.2"
[1] INFO: [WARNING] Unable to load image "quay.io/jetstack/cert-manager-webhook:v1.7.2" into the kind cluster "test-lir5iz": error saving image "quay.io/jetstack/cert-manager-webhook:v1.7.2" to "/tmp/image-tar352871197/image.tar": unable to read image data: Error response from daemon: reference does not exist
[1] INFO: Loading image: "quay.io/jetstack/cert-manager-controller:v1.7.2"
[1] INFO: [WARNING] Unable to load image "quay.io/jetstack/cert-manager-controller:v1.7.2" into the kind cluster "test-lir5iz": error saving image "quay.io/jetstack/cert-manager-controller:v1.7.2" to "/tmp/image-tar2600167839/image.tar": unable to read image data: Error response from daemon: reference does not exist
[1] INFO: Loading image: "registry.k8s.io/cluster-api/cluster-api-controller:v1.1.5"
[1] INFO: [WARNING] Unable to load image "registry.k8s.io/cluster-api/cluster-api-controller:v1.1.5" into the kind cluster "test-lir5iz": error saving image "registry.k8s.io/cluster-api/cluster-api-controller:v1.1.5" to "/tmp/image-tar1811969123/image.tar": unable to read image data: Error response from daemon: reference does not exist
[1] INFO: Loading image: "registry.k8s.io/cluster-api/kubeadm-bootstrap-controller:v1.1.5"
[1] INFO: [WARNING] Unable to load image "registry.k8s.io/cluster-api/kubeadm-bootstrap-controller:v1.1.5" into the kind cluster "test-lir5iz": error saving image "registry.k8s.io/cluster-api/kubeadm-bootstrap-controller:v1.1.5" to "/tmp/image-tar791185115/image.tar": unable to read image data: Error response from daemon: reference does not exist
[1] INFO: Loading image: "registry.k8s.io/cluster-api/kubeadm-control-plane-controller:v1.1.5"
[1] INFO: [WARNING] Unable to load image "registry.k8s.io/cluster-api/kubeadm-control-plane-controller:v1.1.5" into the kind cluster "test-lir5iz": error saving image "registry.k8s.io/cluster-api/kubeadm-control-plane-controller:v1.1.5" to "/tmp/image-tar1286679079/image.tar": unable to read image data: Error response from daemon: reference does not exist
[1] STEP: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
[1] STEP: Writing AWS service quotas to a file for parallel tests
[1] STEP: Initializing the bootstrap cluster
[1] INFO: clusterctl init --core cluster-api --bootstrap kubeadm --control-plane kubeadm --infrastructure aws
[1] STEP: Waiting for provider controllers to be running
[1] STEP: Waiting for deployment capa-system/capa-controller-manager to be available
... skipping 1865 lines ...
[6]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/clusterctl_upgrade.go:147
[6] ------------------------------
[6] 
[6] JUnit report was created: /logs/artifacts/junit.e2e_suite.6.xml
[6] 
[6] Ran 3 of 4 Specs in 4445.588 seconds
[6] SUCCESS! -- 3 Passed | 0 Failed | 1 Pending | 0 Skipped
[6] PASS
[2] STEP: Deleting namespace used for hosting the "clusterctl-upgrade" test spec
[2] INFO: Deleting namespace clusterctl-upgrade-b1aq7h
[2] [AfterEach] Clusterctl Upgrade Spec [from v1alpha4]
[2]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_test.go:158
[2] STEP: Node 2 released resources: {ec2-normal:0, vpc:2, eip:2, ngw:2, igw:2, classiclb:2, ec2-GPU:0, volume-gp2:0}
... skipping 12 lines ...
[2] STEP: Deleting namespace used for hosting the "" test spec
[2] INFO: Deleting namespace functional-efs-support-022gju
[2] 
[2] JUnit report was created: /logs/artifacts/junit.e2e_suite.2.xml
[2] 
[2] Ran 3 of 3 Specs in 4792.101 seconds
[2] SUCCESS! -- 3 Passed | 0 Failed | 0 Pending | 0 Skipped
[2] PASS
[3] STEP: Waiting until nodes are ready
[3] STEP: PASSED!
[3] [AfterEach] Cluster Upgrade Spec - Single control plane with workers [K8s-Upgrade]
[3]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/cluster_upgrade.go:238
[3] STEP: Dumping logs from the "k8s-upgrade-and-conformance-ln54y3" workload cluster
... skipping 84 lines ...
[4]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/cluster_upgrade.go:115
[4] ------------------------------
[4] 
[4] JUnit report was created: /logs/artifacts/junit.e2e_suite.4.xml
[4] 
[4] Ran 4 of 6 Specs in 5383.237 seconds
[4] SUCCESS! -- 4 Passed | 0 Failed | 2 Pending | 0 Skipped
[4] PASS
[3] STEP: Deleting namespace used for hosting the "" test spec
[3] INFO: Deleting namespace functional-test-ignition-cqqucb
[3] 
[3] JUnit report was created: /logs/artifacts/junit.e2e_suite.3.xml
[3] 
[3] Ran 4 of 5 Specs in 5593.015 seconds
[3] SUCCESS! -- 4 Passed | 0 Failed | 1 Pending | 0 Skipped
[3] PASS
[5] STEP: Deleting namespace used for hosting the "" test spec
[5] INFO: Deleting namespace functional-gpu-cluster-h2xgvb
[5] 
[5] JUnit report was created: /logs/artifacts/junit.e2e_suite.5.xml
[5] 
[5] Ran 4 of 4 Specs in 5753.331 seconds
[5] SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped
[5] PASS
[7] [AfterEach] Machine Pool Spec
[7]   /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/e2e/machine_pool.go:128
[7] STEP: Dumping logs from the "machine-pool-3jvaw3" workload cluster
[7] STEP: Dumping all the Cluster API resources in the "machine-pool-xgcdxe" namespace
[7] STEP: Deleting cluster machine-pool-xgcdxe/machine-pool-3jvaw3
... skipping 61 lines ...
[7] 
[7] JUnit report was created: /logs/artifacts/junit.e2e_suite.7.xml
[7] 
[7] 
[7] Summarizing 1 Failure:
[7] 
[7] [Fail] [unmanaged] [Cluster API Framework] Machine Pool Spec [It] Should successfully create a cluster with machine pool machines 
[7] /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.5/framework/machinepool_helpers.go:90
[7] 
[7] Ran 3 of 3 Specs in 6979.055 seconds
[7] FAIL! -- 2 Passed | 1 Failed | 0 Pending | 0 Skipped
[7] --- FAIL: TestE2E (6979.08s)
[7] FAIL
[1] folder created for eks clusters: /logs/artifacts/clusters/bootstrap/aws-resources
[1] STEP: Tearing down the management cluster
[1] STEP: Deleting cluster-api-provider-aws-sigs-k8s-io CloudFormation stack
[1] 
[1] JUnit report was created: /logs/artifacts/junit.e2e_suite.1.xml
[1] 
[1] Ran 3 of 3 Specs in 7427.060 seconds
[1] SUCCESS! -- 3 Passed | 0 Failed | 0 Pending | 0 Skipped
[1] PASS

Ginkgo ran 1 suite in 2h5m19.674729008s
Test Suite Failed

Ginkgo 2.0 is coming soon!
==========================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
... skipping 3 lines ...
To silence this notice, set the environment variable: ACK_GINKGO_RC=true
Alternatively you can: touch $HOME/.ack-ginkgo-rc

real	125m19.684s
user	28m10.336s
sys	7m28.142s
make: *** [Makefile:409: test-e2e] Error 1
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
Cleaning up after docker
Stopping Docker: dockerProgram process in pidfile '/var/run/docker-ssd.pid', 1 process(es), refused to die.
... skipping 3 lines ...