This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 8 succeeded
Started2022-06-22 20:46
Elapsed3h3m
Revisionrelease-0.6

Test Failures


capa-e2e functional tests - unmanaged Upgrade to master Kubernetes in same namespace should create the clusters 28m24s

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
				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files


Show 8 Passed Tests

Show 5 Skipped Tests

Error lines from build-log.txt

... skipping 844 lines ...
STEP: Creating a clusterctl local repository into "/logs/artifacts"
STEP: Reading the CNI manifest ../../data/cni/calico.yaml
STEP: 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
STEP: Setting environment variable: key=AWS_B64ENCODED_CREDENTIALS, value=*******
STEP: Initializing the bootstrap cluster
INFO: clusterctl init --core cluster-api --bootstrap kubeadm --control-plane kubeadm --infrastructure aws
STEP: Waiting for provider controllers to be running
STEP: 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
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:200
    It should be creatable and deletable
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:201
------------------------------
functional tests - unmanaged MachineDeployment misconfigurations 
  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
[BeforeEach] functional tests - unmanaged
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:88
STEP: 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
STEP: 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 ...

• [SLOW TEST:1092.852 seconds]
functional tests - unmanaged
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:81
  MachineDeployment misconfigurations
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:226
    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
------------------------------
functional tests - unmanaged Workload cluster in multiple AZs 
  It should be creatable and deletable
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_test.go:271
[BeforeEach] functional tests - unmanaged
... skipping 129 lines ...
INFO: Waiting for the machine deployments to be provisioned
STEP: Waiting for the workload nodes to exist
INFO: Waiting for the machine pools to be provisioned
STEP: Deleting node directly from infra cloud
STEP: Terminating EC2 instance with ID: aws:///us-west-2a/i-04aac7f6b48db20a6
STEP: Waiting for AWSMachine to be labelled as terminated
STEP: Waiting for machine to reach Failed state
STEP: Deleting the clusters and namespaces
STEP: Deleting cluster cluster-7czy2n
STEP: Waiting for cluster cluster-7czy2n to be deleted
STEP: Deleting cluster cluster-sokvad
STEP: 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


Summarizing 1 Failure:

[Fail] functional tests - unmanaged Upgrade to master Kubernetes in same namespace [It] should create the clusters 
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api@v0.3.22/test/framework/machinedeployment_helpers.go:121

Ran 9 of 14 Specs in 10769.847 seconds
FAIL! -- 8 Passed | 1 Failed | 0 Pending | 5 Skipped
--- 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 ...