This job view page is being replaced by Spyglass soon. Check out the new job view.
PRLochanRn: Availability zones support for managed clusters
ResultFAILURE
Tests 1 failed / 0 succeeded
Started2021-07-28 22:52
Elapsed38m17s
Revisionb1bc1c59ecb7888a80577c0bc575c152dda15b51
Refs 1564

Test Failures


capz-e2e Workload cluster creation Creating an AKS cluster with a single control plane node and 1 node 30m36s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sWorkload\scluster\screation\sCreating\san\sAKS\scluster\swith\sa\ssingle\scontrol\splane\snode\sand\s1\snode$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:450
Timed out after 1200.000s.
Error: Unexpected non-nil/non-zero extra argument at index 1:
	<*errors.errorString>: &errors.errorString{s:"system machine pools not ready"}
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/aks.go:215
				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid


Show 21 Skipped Tests

Error lines from build-log.txt

... skipping 432 lines ...
  with a single control plane node and 1 node
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:450

INFO: "with a single control plane node and 1 node" started at Wed, 28 Jul 2021 22:59:24 UTC on Ginkgo node 1 of 3
STEP: Creating namespace "capz-e2e-s8u49w" for hosting the cluster
Jul 28 22:59:24.694: INFO: starting to create namespace for hosting the "capz-e2e-s8u49w" test spec
2021/07/28 22:59:24 failed trying to get namespace (capz-e2e-s8u49w):namespaces "capz-e2e-s8u49w" not found
INFO: Creating namespace capz-e2e-s8u49w
INFO: Creating event watcher for namespace "capz-e2e-s8u49w"
INFO: Cluster name is capz-e2e-s8u49w-aks
INFO: Creating the workload cluster with name "capz-e2e-s8u49w-aks" using the "aks-multi-tenancy" template (Kubernetes v1.19.9, 1 control-plane machines, 1 worker machines)
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster capz-e2e-s8u49w-aks --infrastructure (default) --kubernetes-version v1.19.9 --control-plane-machine-count 1 --worker-machine-count 1 --flavor aks-multi-tenancy
... skipping 47 lines ...
  Creating an AKS cluster
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:449
    with a single control plane node and 1 node [It]
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:450

    Timed out after 1200.000s.
    Error: Unexpected non-nil/non-zero extra argument at index 1:
    	<*errors.errorString>: &errors.errorString{s:"system machine pools not ready"}

    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/aks.go:215

    Full Stack Trace
    sigs.k8s.io/cluster-api-provider-azure/test/e2e.WaitForControlPlaneMachinesToExist(0x24f76a0, 0xc000126018, 0x7f6da8399ce0, 0xc000572230, 0x7f6da80955f0, 0xc000572230, 0xc001154d80, 0xc0006e84c8, 0x13, 0xc001e62460, ...)
... skipping 40 lines ...
STEP: Tearing down the management cluster



Summarizing 1 Failure:

[Fail] Workload cluster creation Creating an AKS cluster [It] with a single control plane node and 1 node 
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/aks.go:215

Ran 1 of 22 Specs in 1958.300 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 21 Skipped


Ginkgo ran 1 suite in 34m7.141443958s
Test Suite Failed
make[1]: *** [Makefile:173: test-e2e-run] Error 1
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make: *** [Makefile:181: test-e2e] Error 2
================ REDACTING LOGS ================
All sensitive variables are redacted
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
... skipping 5 lines ...