periodic-cluster-api-provider-aws-e2e-clusterclass #1619374076365639680
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 2 failed / 64 succeeded |
| Started | |
| Elapsed | 1h8m |
| Revision | main |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capa\-e2e\s\[It\]\s\[unmanaged\]\s\[functional\]\sMultitenancy\stest\sshould\screate\scluster\swith\snested\sassumed\srole$'
[FAILED] Timed out after 10.001s.
Failed to apply the cluster template
Expected success, but got an error:
<*errors.withStack | 0xc000e03800>: {
error: <*exec.ExitError | 0xc000c2c8c0>{
ProcessState: {
pid: 32076,
status: 256,
rusage: {
Utime: {Sec: 0, Usec: 665264},
Stime: {Sec: 0, Usec: 316021},
Maxrss: 100572,
Ixrss: 0,
Idrss: 0,
Isrss: 0,
Minflt: 15786,
Majflt: 0,
Nswap: 0,
Inblock: 0,
Oublock: 25136,
Msgsnd: 0,
Msgrcv: 0,
Nsignals: 0,
Nvcsw: 2498,
Nivcsw: 1636,
},
},
Stderr: nil,
},
stack: [0x1be5460, 0x1be59d1, 0x1d5a40c, 0x2191c93, 0x4db565, 0x4daa5c, 0xa35e9a, 0xa36b0e, 0xa344cd, 0x219116c, 0x2272fd8, 0xa11f5b, 0xa26058, 0x4704e1],
}
exit status 1
In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/clusterctl/clusterctl_helpers.go:308 @ 01/28/23 16:47:20.688
Error from server (AlreadyExists): error when creating "STDIN": awsclusterroleidentities.infrastructure.cluster.x-k8s.io "capamultitenancynested" already exists
> Enter [BeforeEach] [unmanaged] [functional] - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:55 @ 01/28/23 16:46:53.067
< Exit [BeforeEach] [unmanaged] [functional] - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:55 @ 01/28/23 16:46:53.067 (0s)
> Enter [It] should create cluster with nested assumed role - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:161 @ 01/28/23 16:46:53.067
STEP: Node 19 acquiring resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/resource.go:187 @ 01/28/23 16:46:53.09
STEP: Node 19 acquired resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/resource.go:216 @ 01/28/23 16:46:54.092
STEP: Creating a namespace for hosting the "functional-multitenancy-nested" test spec - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/common.go:52 @ 01/28/23 16:46:54.092
INFO: Creating namespace functional-multitenancy-nested-emw3il
INFO: Creating event watcher for namespace "functional-multitenancy-nested-emw3il"
Jan 28 16:46:54.508: INFO: Setting environment variable: key=MULTI_TENANCY_SIMPLE_ROLE_ARN, value=arn:aws:iam::714408958238:role/CAPAMultiTenancySimple
Jan 28 16:46:54.508: INFO: Setting environment variable: key=MULTI_TENANCY_SIMPLE_ROLE_NAME, value=CAPAMultiTenancySimple
Jan 28 16:46:54.508: INFO: Setting environment variable: key=MULTI_TENANCY_SIMPLE_IDENTITY_NAME, value=capamultitenancysimple
Jan 28 16:46:54.570: INFO: Setting environment variable: key=MULTI_TENANCY_JUMP_ROLE_ARN, value=arn:aws:iam::714408958238:role/CAPAMultiTenancyJump
Jan 28 16:46:54.570: INFO: Setting environment variable: key=MULTI_TENANCY_JUMP_ROLE_NAME, value=CAPAMultiTenancyJump
Jan 28 16:46:54.570: INFO: Setting environment variable: key=MULTI_TENANCY_JUMP_IDENTITY_NAME, value=capamultitenancyjump
Jan 28 16:46:54.624: INFO: Setting environment variable: key=MULTI_TENANCY_NESTED_ROLE_ARN, value=arn:aws:iam::714408958238:role/CAPAMultiTenancyNested
Jan 28 16:46:54.624: INFO: Setting environment variable: key=MULTI_TENANCY_NESTED_ROLE_NAME, value=CAPAMultiTenancyNested
Jan 28 16:46:54.624: INFO: Setting environment variable: key=MULTI_TENANCY_NESTED_IDENTITY_NAME, value=capamultitenancynested
STEP: Creating cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:171 @ 01/28/23 16:46:54.624
INFO: Creating the workload cluster with name "functional-multitenancy-nested-rvosow" using the "nested-multitenancy" template (Kubernetes v1.25.3, 1 control-plane machines, 0 worker machines)
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster functional-multitenancy-nested-rvosow --infrastructure (default) --kubernetes-version v1.25.3 --control-plane-machine-count 1 --worker-machine-count 0 --flavor nested-multitenancy
INFO: Applying the cluster template yaml to the cluster
STEP: Dumping all the Cluster API resources in the "functional-multitenancy-nested-emw3il" namespace - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/common.go:68 @ 01/28/23 16:47:06.098
STEP: Dumping all EC2 instances in the "functional-multitenancy-nested-emw3il" namespace - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/common.go:72 @ 01/28/23 16:47:08.513
STEP: Deleting all clusters in the "functional-multitenancy-nested-emw3il" namespace with intervals ["20m" "10s"] - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/common.go:76 @ 01/28/23 16:47:08.935
STEP: Deleting cluster functional-multitenancy-nested-rvosow - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/ginkgoextensions/output.go:35 @ 01/28/23 16:47:09.198
INFO: Waiting for the Cluster functional-multitenancy-nested-emw3il/functional-multitenancy-nested-rvosow to be deleted
STEP: Waiting for cluster functional-multitenancy-nested-rvosow to be deleted - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/ginkgoextensions/output.go:35 @ 01/28/23 16:47:09.414
STEP: Deleting namespace used for hosting the "" test spec - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/common.go:82 @ 01/28/23 16:47:19.614
INFO: Deleting namespace functional-multitenancy-nested-emw3il
STEP: Node 19 released resources: {ec2-normal:0, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/resource.go:269 @ 01/28/23 16:47:20.688
[FAILED] Timed out after 10.001s.
Failed to apply the cluster template
Expected success, but got an error:
<*errors.withStack | 0xc000e03800>: {
error: <*exec.ExitError | 0xc000c2c8c0>{
ProcessState: {
pid: 32076,
status: 256,
rusage: {
Utime: {Sec: 0, Usec: 665264},
Stime: {Sec: 0, Usec: 316021},
Maxrss: 100572,
Ixrss: 0,
Idrss: 0,
Isrss: 0,
Minflt: 15786,
Majflt: 0,
Nswap: 0,
Inblock: 0,
Oublock: 25136,
Msgsnd: 0,
Msgrcv: 0,
Nsignals: 0,
Nvcsw: 2498,
Nivcsw: 1636,
},
},
Stderr: nil,
},
stack: [0x1be5460, 0x1be59d1, 0x1d5a40c, 0x2191c93, 0x4db565, 0x4daa5c, 0xa35e9a, 0xa36b0e, 0xa344cd, 0x219116c, 0x2272fd8, 0xa11f5b, 0xa26058, 0x4704e1],
}
exit status 1
In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/clusterctl/clusterctl_helpers.go:308 @ 01/28/23 16:47:20.688
< Exit [It] should create cluster with nested assumed role - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_test.go:161 @ 01/28/23 16:47:20.688 (27.621s)
from junit.e2e_suite.xml
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capa\-e2e\s\[It\]\s\[unmanaged\]\s\[functional\]\s\[ClusterClass\]\sMultitenancy\stest\s\[ClusterClass\]\sshould\screate\scluster\swith\snested\sassumed\srole$'
[FAILED] Timed out after 10.001s.
Failed to apply the cluster template
Expected success, but got an error:
<*errors.withStack | 0xc001987770>: {
error: <*exec.ExitError | 0xc000850d80>{
ProcessState: {
pid: 32095,
status: 256,
rusage: {
Utime: {Sec: 0, Usec: 632875},
Stime: {Sec: 0, Usec: 255632},
Maxrss: 109220,
Ixrss: 0,
Idrss: 0,
Isrss: 0,
Minflt: 14936,
Majflt: 0,
Nswap: 0,
Inblock: 0,
Oublock: 25136,
Msgsnd: 0,
Msgrcv: 0,
Nsignals: 0,
Nvcsw: 2571,
Nivcsw: 858,
},
},
Stderr: nil,
},
stack: [0x1be5460, 0x1be59d1, 0x1d5a40c, 0x2191c93, 0x4db565, 0x4daa5c, 0xa35e9a, 0xa36b0e, 0xa344cd, 0x219116c, 0x22658f8, 0xa11f5b, 0xa26058, 0x4704e1],
}
exit status 1
In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/clusterctl/clusterctl_helpers.go:308 @ 01/28/23 16:47:21.799
Error from server (AlreadyExists): error when creating "STDIN": awsclusterroleidentities.infrastructure.cluster.x-k8s.io "capamultitenancyjump" already exists
> Enter [BeforeEach] [unmanaged] [functional] [ClusterClass] - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_clusterclass_test.go:47 @ 01/28/23 16:46:52.938
< Exit [BeforeEach] [unmanaged] [functional] [ClusterClass] - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_clusterclass_test.go:47 @ 01/28/23 16:46:52.938 (0s)
> Enter [It] should create cluster with nested assumed role - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_clusterclass_test.go:53 @ 01/28/23 16:46:52.938
STEP: Node 1 acquiring resources: {ec2-normal:2, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/resource.go:187 @ 01/28/23 16:46:52.939
STEP: Node 1 acquired resources: {ec2-normal:2, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/resource.go:216 @ 01/28/23 16:46:53.94
STEP: Creating a namespace for hosting the "functional-multitenancy-nested-clusterclass" test spec - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/common.go:52 @ 01/28/23 16:46:53.94
INFO: Creating namespace functional-multitenancy-nested-clusterclass-yu8xl7
INFO: Creating event watcher for namespace "functional-multitenancy-nested-clusterclass-yu8xl7"
Jan 28 16:46:54.145: INFO: Setting environment variable: key=MULTI_TENANCY_SIMPLE_ROLE_ARN, value=arn:aws:iam::714408958238:role/CAPAMultiTenancySimple
Jan 28 16:46:54.145: INFO: Setting environment variable: key=MULTI_TENANCY_SIMPLE_ROLE_NAME, value=CAPAMultiTenancySimple
Jan 28 16:46:54.145: INFO: Setting environment variable: key=MULTI_TENANCY_SIMPLE_IDENTITY_NAME, value=capamultitenancysimple
Jan 28 16:46:54.203: INFO: Setting environment variable: key=MULTI_TENANCY_JUMP_ROLE_ARN, value=arn:aws:iam::714408958238:role/CAPAMultiTenancyJump
Jan 28 16:46:54.203: INFO: Setting environment variable: key=MULTI_TENANCY_JUMP_ROLE_NAME, value=CAPAMultiTenancyJump
Jan 28 16:46:54.203: INFO: Setting environment variable: key=MULTI_TENANCY_JUMP_IDENTITY_NAME, value=capamultitenancyjump
Jan 28 16:46:54.262: INFO: Setting environment variable: key=MULTI_TENANCY_NESTED_ROLE_ARN, value=arn:aws:iam::714408958238:role/CAPAMultiTenancyNested
Jan 28 16:46:54.262: INFO: Setting environment variable: key=MULTI_TENANCY_NESTED_ROLE_NAME, value=CAPAMultiTenancyNested
Jan 28 16:46:54.262: INFO: Setting environment variable: key=MULTI_TENANCY_NESTED_IDENTITY_NAME, value=capamultitenancynested
STEP: Creating cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_clusterclass_test.go:64 @ 01/28/23 16:46:54.262
INFO: Creating the workload cluster with name "cluster-l5asuk" using the "nested-multitenancy-clusterclass" template (Kubernetes v1.25.3, 1 control-plane machines, 0 worker machines)
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster cluster-l5asuk --infrastructure (default) --kubernetes-version v1.25.3 --control-plane-machine-count 1 --worker-machine-count 0 --flavor nested-multitenancy-clusterclass
INFO: Applying the cluster template yaml to the cluster
STEP: Dumping all the Cluster API resources in the "functional-multitenancy-nested-clusterclass-yu8xl7" namespace - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/common.go:68 @ 01/28/23 16:47:06.169
STEP: Dumping all EC2 instances in the "functional-multitenancy-nested-clusterclass-yu8xl7" namespace - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/common.go:72 @ 01/28/23 16:47:09.269
STEP: Deleting all clusters in the "functional-multitenancy-nested-clusterclass-yu8xl7" namespace with intervals ["20m" "10s"] - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/common.go:76 @ 01/28/23 16:47:10.373
STEP: Deleting cluster cluster-l5asuk - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/ginkgoextensions/output.go:35 @ 01/28/23 16:47:10.58
INFO: Waiting for the Cluster functional-multitenancy-nested-clusterclass-yu8xl7/cluster-l5asuk to be deleted
STEP: Waiting for cluster cluster-l5asuk to be deleted - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/ginkgoextensions/output.go:35 @ 01/28/23 16:47:10.705
STEP: Deleting namespace used for hosting the "" test spec - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/common.go:82 @ 01/28/23 16:47:20.768
INFO: Deleting namespace functional-multitenancy-nested-clusterclass-yu8xl7
STEP: Node 1 released resources: {ec2-normal:2, vpc:1, eip:1, ngw:1, igw:1, classiclb:1, ec2-GPU:0, volume-gp2:0} - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/shared/resource.go:269 @ 01/28/23 16:47:21.798
[FAILED] Timed out after 10.001s.
Failed to apply the cluster template
Expected success, but got an error:
<*errors.withStack | 0xc001987770>: {
error: <*exec.ExitError | 0xc000850d80>{
ProcessState: {
pid: 32095,
status: 256,
rusage: {
Utime: {Sec: 0, Usec: 632875},
Stime: {Sec: 0, Usec: 255632},
Maxrss: 109220,
Ixrss: 0,
Idrss: 0,
Isrss: 0,
Minflt: 14936,
Majflt: 0,
Nswap: 0,
Inblock: 0,
Oublock: 25136,
Msgsnd: 0,
Msgrcv: 0,
Nsignals: 0,
Nvcsw: 2571,
Nivcsw: 858,
},
},
Stderr: nil,
},
stack: [0x1be5460, 0x1be59d1, 0x1d5a40c, 0x2191c93, 0x4db565, 0x4daa5c, 0xa35e9a, 0xa36b0e, 0xa344cd, 0x219116c, 0x22658f8, 0xa11f5b, 0xa26058, 0x4704e1],
}
exit status 1
In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/clusterctl/clusterctl_helpers.go:308 @ 01/28/23 16:47:21.799
< Exit [It] should create cluster with nested assumed role - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/unmanaged/unmanaged_functional_clusterclass_test.go:53 @ 01/28/23 16:47:21.799 (28.861s)
from junit.e2e_suite.xml
Filter through log files | View test history on testgrid
capa-e2e [It] [unmanaged] [Cluster API Framework] Cluster Upgrade Spec - HA Control Plane Cluster [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capa-e2e [It] [unmanaged] [Cluster API Framework] Cluster Upgrade Spec - HA control plane with scale in rollout [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capa-e2e [It] [unmanaged] [Cluster API Framework] Cluster Upgrade Spec - Single control plane with workers [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capa-e2e [It] [unmanaged] [Cluster API Framework] Clusterctl Upgrade Spec [from latest v1beta1 release to v1beta2] Should create a management cluster and then upgrade all the providers
capa-e2e [It] [unmanaged] [Cluster API Framework] Machine Pool Spec Should successfully create a cluster with machine pool machines
capa-e2e [It] [unmanaged] [Cluster API Framework] Machine Remediation Spec Should successfully trigger KCP remediation
capa-e2e [It] [unmanaged] [Cluster API Framework] Machine Remediation Spec Should successfully trigger machine deployment remediation
capa-e2e [It] [unmanaged] [Cluster API Framework] Self Hosted Spec Should pivot the bootstrap cluster to a self-hosted cluster
capa-e2e [It] [unmanaged] [Cluster API Framework] [ClusterClass] Cluster Upgrade Spec - HA control plane with workers [K8s-Upgrade] [ClusterClass] Should create and upgrade a workload cluster and eventually run kubetest
capa-e2e [It] [unmanaged] [Cluster API Framework] [ClusterClass] ClusterClass Changes Spec - SSA immutability checks [ClusterClass] Should successfully rollout the managed topology upon changes to the ClusterClass
capa-e2e [It] [unmanaged] [Cluster API Framework] [ClusterClass] Self Hosted Spec [ClusterClass] Should pivot the bootstrap cluster to a self-hosted cluster
capa-e2e [It] [unmanaged] [Cluster API Framework] [smoke] [PR-Blocking] Running the quick-start spec Should create a workload cluster
capa-e2e [It] [unmanaged] [Cluster API Framework] [smoke] [PR-Blocking] Running the quick-start spec with ClusterClass Should create a workload cluster
capa-e2e [It] [unmanaged] [functional] CSI=external CCM=external AWSCSIMigration=on: upgrade to v1.23 should create volumes dynamically with external cloud provider
capa-e2e [It] [unmanaged] [functional] CSI=external CCM=in-tree AWSCSIMigration=on: upgrade to v1.23 should create volumes dynamically with external cloud provider
capa-e2e [It] [unmanaged] [functional] CSI=in-tree CCM=in-tree AWSCSIMigration=off: upgrade to v1.23 should create volumes dynamically with external cloud provider
capa-e2e [It] [unmanaged] [functional] GPU-enabled cluster test should create cluster with single worker
capa-e2e [It] [unmanaged] [functional] MachineDeployment misconfigurations MachineDeployment misconfigurations
capa-e2e [It] [unmanaged] [functional] Workload cluster with AWS S3 and Ignition parameter It should be creatable and deletable
capa-e2e [It] [unmanaged] [functional] Workload cluster with AWS SSM Parameter as the Secret Backend should be creatable and deletable
capa-e2e [It] [unmanaged] [functional] Workload cluster with EFS driver should pass dynamic provisioning test
capa-e2e [It] [unmanaged] [functional] Workload cluster with spot instances should be creatable and deletable
capa-e2e [It] [unmanaged] [functional] [ClusterClass] Workload cluster with AWS SSM Parameter as the Secret Backend [ClusterClass] should be creatable and deletable
capa-e2e [It] [unmanaged] [functional] [ClusterClass] Workload cluster with external infrastructure [ClusterClass] should create workload cluster in external VPC
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedAfterSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [SynchronizedBeforeSuite]
capa-e2e [It] [unmanaged] [functional] External infrastructure, external security groups, VPC peering, internal ELB and private subnet use only should create external clusters in peered VPC and with an internal ELB and only utilize a private subnet
capa-e2e [It] [unmanaged] [functional] Multiple workload clusters Defining clusters in the same namespace should create the clusters
capa-e2e [It] [unmanaged] [functional] Multiple workload clusters in different namespaces with machine failures should setup namespaces correctly for the two clusters
capa-e2e [It] [unmanaged] [functional] [Serial] Upgrade to main branch Kubernetes in same namespace should create the clusters