This job view page is being replaced by Spyglass soon. Check out the new job view.
PRsedefsavas: Make subnet spec id field required for SSA to work with CC
ResultFAILURE
Tests 1 failed / 25 succeeded
Started2022-09-27 05:36
Elapsed1h35m
Revision042ce4573106a476a8736b27c0250ad1f77ead3a
Refs 3748

Test Failures


capa-e2e [unmanaged] [functional] Workload cluster in multiple AZs It should be creatable and deletable 23s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capa\-e2e\s\[unmanaged\]\s\[functional\]\sWorkload\scluster\sin\smultiple\sAZs\sIt\sshould\sbe\screatable\sand\sdeletable$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:551
Timed out after 10.001s.
Failed to apply the cluster template
Expected success, but got an error:
    <*errors.withStack | 0xc0030612d8>: {
        error: <*exec.ExitError | 0xc002700680>{
            ProcessState: {
                pid: 33899,
                status: 256,
                rusage: {
                    Utime: {Sec: 0, Usec: 317015},
                    Stime: {Sec: 0, Usec: 120960},
                    Maxrss: 108608,
                    Ixrss: 0,
                    Idrss: 0,
                    Isrss: 0,
                    Minflt: 14715,
                    Majflt: 1,
                    Nswap: 0,
                    Inblock: 136,
                    Oublock: 23344,
                    Msgsnd: 0,
                    Msgrcv: 0,
                    Nsignals: 0,
                    Nvcsw: 822,
                    Nivcsw: 121,
                },
            },
            Stderr: nil,
        },
        stack: [0x1b14260, 0x1b147b0, 0x1c8ffcc, 0x2099193, 0x4d7625, 0x4d6b9f, 0x96b051, 0x96b3f9, 0x96b7e5, 0x96b16d, 0x209878c, 0x214c13c, 0x2160d18, 0x948d71, 0x948765, 0x947e5b, 0x94db4a, 0x94d547, 0x9599e8, 0x959705, 0x958da5, 0x95b172, 0x967569, 0x967376, 0x21693bb, 0x520862, 0x46d9a1],
    }
    exit status 1
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/framework/clusterctl/clusterctl_helpers.go:278
				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid


Show 25 Passed Tests

Show 4 Skipped Tests

Error lines from build-log.txt

... skipping 2360 lines ...
[1] INFO: Creating event watcher for namespace "functional-test-multi-az-5ys2u5"
[1] STEP: Creating a cluster
[1] INFO: Creating the workload cluster with name "functional-test-multi-az-257vow" using the "multi-az" template (Kubernetes v1.24.0, 3 control-plane machines, 0 worker machines)
[1] INFO: Getting the cluster template yaml
[1] INFO: clusterctl config cluster functional-test-multi-az-257vow --infrastructure (default) --kubernetes-version v1.24.0 --control-plane-machine-count 3 --worker-machine-count 0 --flavor multi-az
[1] INFO: Applying the cluster template yaml to the cluster
[1] error: error validating "STDIN": error validating data: [ValidationError(AWSCluster.spec.network.subnets[0]): missing required field "id" in io.x-k8s.cluster.infrastructure.v1beta2.AWSCluster.spec.network.subnets, ValidationError(AWSCluster.spec.network.subnets[1]): missing required field "id" in io.x-k8s.cluster.infrastructure.v1beta2.AWSCluster.spec.network.subnets, ValidationError(AWSCluster.spec.network.subnets[2]): missing required field "id" in io.x-k8s.cluster.infrastructure.v1beta2.AWSCluster.spec.network.subnets, ValidationError(AWSCluster.spec.network.subnets[3]): missing required field "id" in io.x-k8s.cluster.infrastructure.v1beta2.AWSCluster.spec.network.subnets]; if you choose to ignore these errors, turn validation off with --validate=false
[1] 
[1] STEP: Dumping all the Cluster API resources in the "functional-test-multi-az-5ys2u5" namespace
[1] STEP: Dumping all EC2 instances in the "functional-test-multi-az-5ys2u5" namespace
[2] STEP: Waiting until nodes are ready
[1] STEP: Deleting all clusters in the "functional-test-multi-az-5ys2u5" namespace with intervals ["20m" "10s"]
[1] STEP: Deleting cluster functional-test-multi-az-257vow
... skipping 18 lines ...
[1]   Workload cluster in multiple AZs
[1]   /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:550
[1]     It should be creatable and deletable [It]
[1]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:551
[1] 
[1]     Timed out after 10.001s.
[1]     Failed to apply the cluster template
[1]     Expected success, but got an error:
[1]         <*errors.withStack | 0xc0030612d8>: {
[1]             error: <*exec.ExitError | 0xc002700680>{
[1]                 ProcessState: {
[1]                     pid: 33899,
[1]                     status: 256,
[1]                     rusage: {
[1]                         Utime: {Sec: 0, Usec: 317015},
[1]                         Stime: {Sec: 0, Usec: 120960},
... skipping 235 lines ...
[4]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:328
[4] ------------------------------
[4] 
[4] JUnit report was created: /logs/artifacts/junit.e2e_suite.4.xml
[4] 
[4] Ran 3 of 3 Specs in 4508.099 seconds
[4] SUCCESS! -- 3 Passed | 0 Failed | 0 Pending | 0 Skipped
[4] PASS
[1] STEP: Checking all the machines controlled by functional-test-spot-instances-c42ltv-md-0 are in the "<None>" failure domain
[1] INFO: Waiting for the machine pools to be provisioned
[1] STEP: Finding EC2 spot instance with ID: aws:///us-west-2a/i-0cc4d7970c1f9f357
[1] STEP: Dumping all the Cluster API resources in the "functional-test-spot-instances-umybb0" namespace
[1] STEP: Dumping all EC2 instances in the "functional-test-spot-instances-umybb0" namespace
... skipping 47 lines ...
[7]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:397
[7] ------------------------------
[7] 
[7] JUnit report was created: /logs/artifacts/junit.e2e_suite.7.xml
[7] 
[7] Ran 4 of 4 Specs in 4609.952 seconds
[7] SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped
[7] PASS
[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}
[2] 
[2] • [SLOW TEST:2597.950 seconds]
[2] [unmanaged] [Cluster API Framework] [ClusterClass]
[2] /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_CAPI_clusterclass_test.go:35
... skipping 3 lines ...
[2]     /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/e2e/cluster_upgrade.go:117
[2] ------------------------------
[2] 
[2] JUnit report was created: /logs/artifacts/junit.e2e_suite.2.xml
[2] 
[2] Ran 3 of 3 Specs in 4610.296 seconds
[2] SUCCESS! -- 3 Passed | 0 Failed | 0 Pending | 0 Skipped
[2] PASS
[6] INFO: Waiting for control plane to be ready
[6] INFO: Waiting for control plane functional-test-ignition-fuvbh2/functional-test-ignition-epohjf-control-plane to be ready (implies underlying nodes to be ready as well)
[6] STEP: Waiting for the control plane to be ready
[6] STEP: Checking all the the control plane machines are in the expected failure domains
[6] INFO: Waiting for the machine deployments to be provisioned
... skipping 24 lines ...
[3]     /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:500
[3] ------------------------------
[3] 
[3] JUnit report was created: /logs/artifacts/junit.e2e_suite.3.xml
[3] 
[3] Ran 4 of 4 Specs in 4705.481 seconds
[3] SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped
[3] PASS
[6] STEP: Deleting all clusters in the "functional-test-ignition-fuvbh2" namespace with intervals ["20m" "10s"]
[6] STEP: Deleting cluster functional-test-ignition-epohjf
[6] INFO: Waiting for the Cluster functional-test-ignition-fuvbh2/functional-test-ignition-epohjf to be deleted
[6] STEP: Waiting for cluster functional-test-ignition-epohjf to be deleted
[1] STEP: Deleting namespace used for hosting the "" test spec
... skipping 16 lines ...
[6] STEP: Deleting namespace used for hosting the "" test spec
[6] INFO: Deleting namespace functional-test-ignition-fuvbh2
[6] 
[6] JUnit report was created: /logs/artifacts/junit.e2e_suite.6.xml
[6] 
[6] Ran 3 of 5 Specs in 4980.641 seconds
[6] SUCCESS! -- 3 Passed | 0 Failed | 2 Pending | 0 Skipped
[6] PASS
[5] STEP: Deleting namespace used for hosting the "" test spec
[5] INFO: Deleting namespace functional-gpu-cluster-jl5aif
[5] 
[5] JUnit report was created: /logs/artifacts/junit.e2e_suite.5.xml
[5] 
[5] Ran 4 of 4 Specs in 5094.907 seconds
[5] SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped
[5] PASS
[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] 
[1] Summarizing 1 Failure:
[1] 
[1] [Fail] [unmanaged] [functional] Workload cluster in multiple AZs [It] It should be creatable and deletable 
[1] /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.0/framework/clusterctl/clusterctl_helpers.go:278
[1] 
[1] Ran 5 of 7 Specs in 5497.667 seconds
[1] FAIL! -- 4 Passed | 1 Failed | 2 Pending | 0 Skipped
[1] --- FAIL: TestE2E (5497.70s)
[1] FAIL

Ginkgo ran 1 suite in 1h33m14.300194275s
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	93m14.310s
user	19m41.961s
sys	5m6.152s
make: *** [Makefile:401: 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 ...