periodic-cluster-api-provider-aws-e2e-release-0-6 #1539711500552245248
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 8 succeeded |
| Started | |
| Elapsed | 3h3m |
| Revision | release-0.6 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capa\-e2e\sfunctional\stests\s\-\sunmanaged\sUpgrade\sto\smaster\sKubernetes\sin\ssame\snamespace\sshould\screate\sthe\sclusters$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:153
Timed out after 600.000s.
Expected
<int>: 0
to equal
<int>: 1
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api@v0.3.22/test/framework/machinedeployment_helpers.go:121
[BeforeEach] functional tests - unmanaged
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:88
�[1mSTEP�[0m: Creating a namespace for hosting the "functional-tests" test spec
INFO: Creating namespace functional-tests-z7va34
INFO: Creating event watcher for namespace "functional-tests-z7va34"
[It] should create the clusters
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:153
�[1mSTEP�[0m: Creating first cluster with single control plane
�[1mSTEP�[0m: Setting environment variable: key=USE_CI_ARTIFACTS, value=true
�[1mSTEP�[0m: Setting environment variable: key=KUBERNETES_VERSION, value=v1.21.3
INFO: Creating the workload cluster with name "cluster-2k6djr" using the "upgrade-to-main" template (Kubernetes v1.21.3, 824652991424 control-plane machines, 824652991440 worker machines)
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster cluster-2k6djr --infrastructure (default) --kubernetes-version v1.21.3 --control-plane-machine-count 1 --worker-machine-count 1 --flavor upgrade-to-main
INFO: Applying the cluster template yaml to the cluster
INFO: Waiting for the cluster infrastructure to be provisioned
�[1mSTEP�[0m: 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 functional-tests-z7va34/cluster-2k6djr-control-plane to be provisioned
�[1mSTEP�[0m: Waiting for one control plane node to exist
INFO: Waiting for control plane to be ready
INFO: Waiting for control plane functional-tests-z7va34/cluster-2k6djr-control-plane to be ready (implies underlying nodes to be ready as well)
�[1mSTEP�[0m: Waiting for the control plane to be ready
INFO: Waiting for the machine deployments to be provisioned
�[1mSTEP�[0m: Waiting for the workload nodes to exist
INFO: Waiting for the machine pools to be provisioned
INFO: Creating the workload cluster with name "cluster-2k6djr" using the "upgrade-ci-artifacts" template (Kubernetes v1.22.12-rc.0.1+46d58cc173c854, 824652991424 control-plane machines, 824652991440 worker machines)
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster cluster-2k6djr --infrastructure (default) --kubernetes-version v1.22.12-rc.0.1+46d58cc173c854 --control-plane-machine-count 1 --worker-machine-count 1 --flavor upgrade-ci-artifacts
INFO: Applying the cluster template yaml to the cluster
INFO: Waiting for the cluster infrastructure to be provisioned
�[1mSTEP�[0m: 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 functional-tests-z7va34/cluster-2k6djr-control-plane to be provisioned
�[1mSTEP�[0m: Waiting for one control plane node to exist
INFO: Waiting for control plane to be ready
INFO: Waiting for control plane functional-tests-z7va34/cluster-2k6djr-control-plane to be ready (implies underlying nodes to be ready as well)
�[1mSTEP�[0m: Waiting for the control plane to be ready
INFO: Waiting for the machine deployments to be provisioned
�[1mSTEP�[0m: Waiting for the workload nodes to exist
[AfterEach] functional tests - unmanaged
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:431
�[1mSTEP�[0m: Dumping all the Cluster API resources in the "functional-tests-z7va34" namespace
�[1mSTEP�[0m: Dumping all EC2 instances in the "functional-tests-z7va34" namespace
�[1mSTEP�[0m: Deleting cluster cluster-2k6djr
INFO: Waiting for the Cluster functional-tests-z7va34/cluster-2k6djr to be deleted
�[1mSTEP�[0m: Waiting for cluster cluster-2k6djr to be deleted
�[1mSTEP�[0m: Deleting namespace used for hosting the "" test spec
INFO: Deleting namespace functional-tests-z7va34
from junit.e2e_suite.1.xml
Filter through log files
capa-e2e functional tests - unmanaged MachineDeployment misconfigurations Should fail to create MachineDeployment with invalid subnet or non-configured Availability Zone
capa-e2e functional tests - unmanaged Multiple workload clusters in different namespaces with machine failures should setup namespaces correctly for the two clusters
capa-e2e functional tests - unmanaged Multiple workload clusters in same namespace should create the clusters
capa-e2e functional tests - unmanaged Multitenancy test should create cluster with assumed role
capa-e2e functional tests - unmanaged Multitenancy test should create cluster with nested assumed role
capa-e2e functional tests - unmanaged Workload cluster in multiple AZs It should be creatable and deletable
capa-e2e functional tests - unmanaged Workload cluster with AWS SSM Parameter as the Secret Backend It should be creatable and deletable
capa-e2e functional tests - unmanaged Workload cluster with spot instances It should be creatable and deletable
capa-e2e Cluster API E2E tests - unmanaged Running the KCP upgrade spec Should successfully upgrade Kubernetes, DNS, kube-proxy, and etcd in a HA cluster
capa-e2e Cluster API E2E tests - unmanaged Running the KCP upgrade spec Should successfully upgrade Kubernetes, DNS, kube-proxy, and etcd in a single control plane cluster
capa-e2e Cluster API E2E tests - unmanaged Running the Machine pool spec Should successfully create a cluster with machine pool machines
capa-e2e Cluster API E2E tests - unmanaged Running the MachineRemediation spec Should successfully remediate unhealthy machines with MachineHealthCheck
capa-e2e Cluster API E2E tests - unmanaged Running the quick-start spec [PR-Blocking] Should create a workload cluster
... skipping 844 lines ... [1mSTEP[0m: Creating a clusterctl local repository into "/logs/artifacts" [1mSTEP[0m: Reading the CNI manifest ../../data/cni/calico.yaml [1mSTEP[0m: Setting up the bootstrap cluster INFO: Creating a kind cluster with name "test-q742e1" INFO: The kubeconfig file for the kind cluster is /tmp/e2e-kind261499769 INFO: Loading image: "gcr.io/k8s-staging-cluster-api/cluster-api-controller:v0.3.22" INFO: [WARNING] Unable to load image "gcr.io/k8s-staging-cluster-api/cluster-api-controller:v0.3.22" into the kind cluster "test-q742e1": stdout: "", stderr: "Error response from daemon: reference does not exist\n": exit status 1 INFO: Loading image: "gcr.io/k8s-staging-cluster-api/kubeadm-bootstrap-controller:v0.3.22" INFO: [WARNING] Unable to load image "gcr.io/k8s-staging-cluster-api/kubeadm-bootstrap-controller:v0.3.22" into the kind cluster "test-q742e1": stdout: "", stderr: "Error response from daemon: reference does not exist\n": exit status 1 INFO: Loading image: "gcr.io/k8s-staging-cluster-api/kubeadm-control-plane-controller:v0.3.22" INFO: [WARNING] Unable to load image "gcr.io/k8s-staging-cluster-api/kubeadm-control-plane-controller:v0.3.22" into the kind cluster "test-q742e1": stdout: "", stderr: "Error response from daemon: reference does not exist\n": exit status 1 INFO: Loading image: "gcr.io/k8s-staging-cluster-api/capa-manager:e2e" INFO: Loading image: "quay.io/jetstack/cert-manager-cainjector:v0.16.1" INFO: [WARNING] Unable to load image "quay.io/jetstack/cert-manager-cainjector:v0.16.1" into the kind cluster "test-q742e1": stdout: "", stderr: "Error response from daemon: reference does not exist\n": exit status 1 INFO: Loading image: "quay.io/jetstack/cert-manager-webhook:v0.16.1" INFO: [WARNING] Unable to load image "quay.io/jetstack/cert-manager-webhook:v0.16.1" into the kind cluster "test-q742e1": stdout: "", stderr: "Error response from daemon: reference does not exist\n": exit status 1 INFO: Loading image: "quay.io/jetstack/cert-manager-controller:v0.16.1" INFO: [WARNING] Unable to load image "quay.io/jetstack/cert-manager-controller:v0.16.1" into the kind cluster "test-q742e1": stdout: "", stderr: "Error response from daemon: reference does not exist\n": exit status 1 [1mSTEP[0m: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=******* [1mSTEP[0m: Initializing the bootstrap cluster INFO: clusterctl init --core cluster-api --bootstrap kubeadm --control-plane kubeadm --infrastructure aws [1mSTEP[0m: Waiting for provider controllers to be running [1mSTEP[0m: Waiting for deployment capa-system/capa-controller-manager to be available INFO: Creating log watcher for controller capa-system/capa-controller-manager, pod capa-controller-manager-8d5f55589-w8lvl, container manager ... skipping 337 lines ... Workload cluster with AWS SSM Parameter as the Secret Backend [90m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:200[0m It should be creatable and deletable [90m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:201[0m [90m------------------------------[0m [0mfunctional tests - unmanaged[0m [90mMachineDeployment misconfigurations[0m [1mShould fail to create MachineDeployment with invalid subnet or non-configured Availability Zone[0m [37m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:227[0m [BeforeEach] functional tests - unmanaged /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:88 [1mSTEP[0m: Creating a namespace for hosting the "functional-tests" test spec INFO: Creating namespace functional-tests-anxzgz INFO: Creating event watcher for namespace "functional-tests-anxzgz" [It] Should fail to create MachineDeployment with invalid subnet or non-configured Availability Zone /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:227 [1mSTEP[0m: Creating a cluster INFO: Creating the workload cluster with name "cluster-phb74o" using the "(default)" template (Kubernetes v1.21.3, 824659916800 control-plane machines, 824659916808 worker machines) INFO: Getting the cluster template yaml INFO: clusterctl config cluster cluster-phb74o --infrastructure (default) --kubernetes-version v1.21.3 --control-plane-machine-count 1 --worker-machine-count 0 --flavor (default) INFO: Applying the cluster template yaml to the cluster ... skipping 40 lines ... [32m• [SLOW TEST:1092.852 seconds][0m functional tests - unmanaged [90m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:81[0m MachineDeployment misconfigurations [90m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:226[0m Should fail to create MachineDeployment with invalid subnet or non-configured Availability Zone [90m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:227[0m [90m------------------------------[0m [0mfunctional tests - unmanaged[0m [90mWorkload cluster in multiple AZs[0m [1mIt should be creatable and deletable[0m [37m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:271[0m [BeforeEach] functional tests - unmanaged ... skipping 129 lines ... INFO: Waiting for the machine deployments to be provisioned [1mSTEP[0m: Waiting for the workload nodes to exist INFO: Waiting for the machine pools to be provisioned [1mSTEP[0m: Deleting node directly from infra cloud [1mSTEP[0m: Terminating EC2 instance with ID: aws:///us-west-2a/i-04aac7f6b48db20a6 [1mSTEP[0m: Waiting for AWSMachine to be labelled as terminated [1mSTEP[0m: Waiting for machine to reach Failed state [1mSTEP[0m: Deleting the clusters and namespaces [1mSTEP[0m: Deleting cluster cluster-7czy2n [1mSTEP[0m: Waiting for cluster cluster-7czy2n to be deleted [1mSTEP[0m: Deleting cluster cluster-sokvad [1mSTEP[0m: Waiting for cluster cluster-sokvad to be deleted INFO: Deleting namespace multi-workload-y1oqwl ... skipping 160 lines ... JUnit report was created: /logs/artifacts/junit.e2e_suite.1.xml [91m[1mSummarizing 1 Failure:[0m [91m[1m[Fail] [0m[90mfunctional tests - unmanaged [0m[0mUpgrade to master Kubernetes [0m[90min same namespace [0m[91m[1m[It] should create the clusters [0m [37m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api@v0.3.22/test/framework/machinedeployment_helpers.go:121[0m [1m[91mRan 9 of 14 Specs in 10769.847 seconds[0m [1m[91mFAIL![0m -- [32m[1m8 Passed[0m | [91m[1m1 Failed[0m | [33m[1m0 Pending[0m | [36m[1m5 Skipped[0m --- FAIL: TestE2E (10769.85s) FAIL Ginkgo ran 1 suite in 3h0m36.181113463s Test Suite Failed real 180m36.188s user 11m10.222s sys 2m41.637s make: *** [Makefile:156: 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 ...