capz-conformance-1-24 #1619952142259326976
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 2 succeeded |
| Started | |
| Elapsed | 29m23s |
| Revision | release-1.7 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\s\[It\]\sConformance\sTests\sconformance\-tests$'
[FAILED] Timed out after 1200.001s.
Timed out waiting for Cluster capz-conf-a6xre8/capz-conf-a6xre8 to provision
Expected
<string>: Provisioning
to equal
<string>: Provisioned
In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/cluster_helpers.go:144 @ 01/30/23 07:23:28.314
There were additional failures detected after the initial failure. These are visible in the timeline
> Enter [BeforeEach] Conformance Tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:56 @ 01/30/23 07:03:25.413
INFO: Cluster name is capz-conf-a6xre8
STEP: Creating namespace "capz-conf-a6xre8" for hosting the cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:88 @ 01/30/23 07:03:25.413
Jan 30 07:03:25.413: INFO: starting to create namespace for hosting the "capz-conf-a6xre8" test spec
INFO: Creating namespace capz-conf-a6xre8
INFO: Creating event watcher for namespace "capz-conf-a6xre8"
< Exit [BeforeEach] Conformance Tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:56 @ 01/30/23 07:03:25.458 (45ms)
> Enter [It] conformance-tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:100 @ 01/30/23 07:03:25.458
conformance-tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:102 @ 01/30/23 07:03:25.458
conformance-tests
Name | N | Min | Median | Mean | StdDev | Max
INFO: Creating the workload cluster with name "capz-conf-a6xre8" using the "conformance-ci-artifacts" template (Kubernetes v1.24.11-rc.0.6+7c685ed7305e76, 1 control-plane machines, 2 worker machines)
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster capz-conf-a6xre8 --infrastructure (default) --kubernetes-version v1.24.11-rc.0.6+7c685ed7305e76 --control-plane-machine-count 1 --worker-machine-count 2 --flavor conformance-ci-artifacts
INFO: Applying the cluster template yaml to the cluster
INFO: Waiting for the cluster infrastructure to be provisioned
STEP: Waiting for cluster to enter the provisioned phase - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/cluster_helpers.go:134 @ 01/30/23 07:03:28.312
[FAILED] Timed out after 1200.001s.
Timed out waiting for Cluster capz-conf-a6xre8/capz-conf-a6xre8 to provision
Expected
<string>: Provisioning
to equal
<string>: Provisioned
In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/cluster_helpers.go:144 @ 01/30/23 07:23:28.314
< Exit [It] conformance-tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:100 @ 01/30/23 07:23:28.314 (20m2.856s)
> Enter [AfterEach] Conformance Tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:242 @ 01/30/23 07:23:28.314
Jan 30 07:23:28.329: INFO: FAILED!
Jan 30 07:23:28.329: INFO: Cleaning up after "Conformance Tests conformance-tests" spec
STEP: Unable to dump workload cluster logs as the cluster is nil - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:148 @ 01/30/23 07:23:28.329
Jan 30 07:23:28.329: INFO: Dumping all the Cluster API resources in the "capz-conf-a6xre8" namespace
Jan 30 07:23:28.725: INFO: Deleting all clusters in the capz-conf-a6xre8 namespace
STEP: Redacting sensitive information from logs - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:212 @ 01/30/23 07:23:28.725
[PANICKED] Test Panicked
In [AfterEach] at: /usr/local/go/src/runtime/panic.go:260 @ 01/30/23 07:23:32.672
runtime error: invalid memory address or nil pointer dereference
Full Stack Trace
sigs.k8s.io/cluster-api-provider-azure/test/e2e.dumpSpecResourcesAndCleanup({0x4305340, 0xc0000620b0}, {{0x3e50d9a, 0x11}, {0x43179b0, 0xc0018a7b70}, {0xc000f29500, 0xf}, 0xc0010c91e0, 0xc0026f5930, ...})
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:171 +0x4ad
sigs.k8s.io/cluster-api-provider-azure/test/e2e.glob..func3.3()
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:262 +0x288
< Exit [AfterEach] Conformance Tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:242 @ 01/30/23 07:23:32.672 (4.358s)
from junit.e2e_suite.1.xml
Filter through log files | View test history on testgrid
capz-e2e [SynchronizedAfterSuite]
capz-e2e [SynchronizedBeforeSuite]
capz-e2e [It] Running the Cluster API E2E tests Running KCP upgrade in a HA cluster [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e [It] Running the Cluster API E2E tests Running KCP upgrade in a HA cluster using scale in rollout [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e [It] Running the Cluster API E2E tests Running the MachineDeployment rollout spec Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
capz-e2e [It] Running the Cluster API E2E tests Running the quick-start spec Should create a workload cluster
capz-e2e [It] Running the Cluster API E2E tests Running the workload cluster upgrade spec [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e [It] Running the Cluster API E2E tests Should successfully exercise machine pools Should successfully create a cluster with machine pool machines
capz-e2e [It] Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger KCP remediation
capz-e2e [It] Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger machine deployment remediation
capz-e2e [It] Running the Cluster API E2E tests Should successfully scale out and scale in a MachineDeployment Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count
capz-e2e [It] Running the Cluster API E2E tests Should successfully set and use node drain timeout A node should be forcefully removed if it cannot be drained in time
capz-e2e [It] Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] with a single control plane node and 1 node
capz-e2e [It] Workload cluster creation Creating a VMSS cluster [REQUIRED] with a single control plane node and an AzureMachinePool with 2 Linux and 2 Windows worker nodes
capz-e2e [It] Workload cluster creation Creating a cluster that uses the external cloud provider and external azurediskcsi driver [OPTIONAL] with a 1 control plane nodes and 2 worker nodes
capz-e2e [It] Workload cluster creation Creating a cluster that uses the external cloud provider and machinepools [OPTIONAL] with 1 control plane node and 1 machinepool
capz-e2e [It] Workload cluster creation Creating a dual-stack cluster [OPTIONAL] With dual-stack worker node
capz-e2e [It] Workload cluster creation Creating a highly available cluster [REQUIRED] With 3 control-plane nodes and 2 Linux and 2 Windows worker nodes
capz-e2e [It] Workload cluster creation Creating a ipv6 control-plane cluster [REQUIRED] With ipv6 worker node
capz-e2e [It] Workload cluster creation Creating an AKS cluster [EXPERIMENTAL][Managed Kubernetes] with a single control plane node and 1 node
capz-e2e [It] Workload cluster creation Creating clusters using clusterclass [OPTIONAL] with a single control plane node, one linux worker node, and one windows worker node
capz-e2e [It] [K8s-Upgrade] Running the CSI migration tests [CSI Migration] Running CSI migration test CSI=external CCM=external AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with out-of-tree cloud provider
capz-e2e [It] [K8s-Upgrade] Running the CSI migration tests [CSI Migration] Running CSI migration test CSI=external CCM=internal AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with intree cloud provider
capz-e2e [It] [K8s-Upgrade] Running the CSI migration tests [CSI Migration] Running CSI migration test CSI=internal CCM=internal AzureDiskCSIMigration=false: upgrade to v1.23 should create volumes dynamically with intree cloud provider
... skipping 486 lines ... [38;5;243m------------------------------[0m [0mConformance Tests [0m[1mconformance-tests[0m [38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:100[0m INFO: Cluster name is capz-conf-a6xre8 [1mSTEP:[0m Creating namespace "capz-conf-a6xre8" for hosting the cluster [38;5;243m@ 01/30/23 07:03:25.413[0m Jan 30 07:03:25.413: INFO: starting to create namespace for hosting the "capz-conf-a6xre8" test spec 2023/01/30 07:03:25 failed trying to get namespace (capz-conf-a6xre8):namespaces "capz-conf-a6xre8" not found INFO: Creating namespace capz-conf-a6xre8 INFO: Creating event watcher for namespace "capz-conf-a6xre8" [1mconformance-tests[38;5;243m - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:102 @ 01/30/23 07:03:25.458[0m [1mconformance-tests [0m[1mName[0m | [1mN[0m | [1mMin[0m | [1mMedian[0m | [1mMean[0m | [1mStdDev[0m | [1mMax[0m INFO: Creating the workload cluster with name "capz-conf-a6xre8" using the "conformance-ci-artifacts" template (Kubernetes v1.24.11-rc.0.6+7c685ed7305e76, 1 control-plane machines, 2 worker machines) ... skipping 20 lines ... configmap/containerd-logger-capz-conf-a6xre8 created clusterresourceset.addons.cluster.x-k8s.io/metrics-server-capz-conf-a6xre8 created configmap/metrics-server-capz-conf-a6xre8 created INFO: Waiting for the cluster infrastructure to be provisioned [1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/30/23 07:03:28.312[0m [38;5;9m[FAILED][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/cluster_helpers.go:144 [38;5;243m@ 01/30/23 07:23:28.314[0m Jan 30 07:23:28.329: INFO: FAILED! Jan 30 07:23:28.329: INFO: Cleaning up after "Conformance Tests conformance-tests" spec [1mSTEP:[0m Unable to dump workload cluster logs as the cluster is nil [38;5;243m@ 01/30/23 07:23:28.329[0m Jan 30 07:23:28.329: INFO: Dumping all the Cluster API resources in the "capz-conf-a6xre8" namespace Jan 30 07:23:28.725: INFO: Deleting all clusters in the capz-conf-a6xre8 namespace [1mSTEP:[0m Redacting sensitive information from logs [38;5;243m@ 01/30/23 07:23:28.725[0m [38;5;13m[PANICKED][0m in [AfterEach] - /usr/local/go/src/runtime/panic.go:260 [38;5;243m@ 01/30/23 07:23:32.672[0m [38;5;9m• [FAILED] [1207.259 seconds][0m [0mConformance Tests [38;5;9m[1m[It] conformance-tests[0m [38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:100[0m [38;5;9m[FAILED] Timed out after 1200.001s. Timed out waiting for Cluster capz-conf-a6xre8/capz-conf-a6xre8 to provision Expected <string>: Provisioning to equal <string>: Provisioned[0m [38;5;9mIn [1m[It][0m[38;5;9m at: [1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/cluster_helpers.go:144[0m [38;5;243m@ 01/30/23 07:23:28.314[0m ... skipping 18 lines ... [0m[1m[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report[0m [38;5;243mautogenerated by Ginkgo[0m [38;5;10m[ReportAfterSuite] PASSED [0.002 seconds][0m [38;5;243m------------------------------[0m [38;5;9m[1mSummarizing 1 Failure:[0m [38;5;9m[FAIL][0m [0mConformance Tests [38;5;9m[1m[It] conformance-tests[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/cluster_helpers.go:144[0m [38;5;9m[1mRan 1 of 23 Specs in 1349.629 seconds[0m [38;5;9m[1mFAIL![0m -- [38;5;10m[1m0 Passed[0m | [38;5;9m[1m1 Failed[0m | [38;5;11m[1m0 Pending[0m | [38;5;14m[1m22 Skipped[0m --- FAIL: TestE2E (1349.63s) FAIL [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11mCurrentGinkgoTestDescription() is deprecated in Ginkgo V2. Use CurrentSpecReport() instead.[0m [1mLearn more at:[0m [38;5;14m[4mhttps://onsi.github.io/ginkgo/MIGRATING_TO_V2#changed-currentginkgotestdescription[0m [38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:278[0m [38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:281[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.6.0[0m Ginkgo ran 1 suite in 24m51.419631091s Test Suite Failed make[2]: *** [Makefile:655: test-e2e-run] Error 1 make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' make[1]: *** [Makefile:670: test-e2e-skip-push] Error 2 make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' make: *** [Makefile:686: test-conformance] Error 2 ================ REDACTING LOGS ================ All sensitive variables are redacted + EXIT_VALUE=2 + set +o xtrace Cleaning up after docker in docker. ================================================================================ ... skipping 5 lines ...