This job view page is being replaced by Spyglass soon. Check out the new job view.
PRkaruppiah7890: Fix resource group not getting updated if tags are added
ResultFAILURE
Tests 1 failed / 0 succeeded
Started2021-10-15 12:50
Elapsed37m29s
Revisionc366a32c78186b71e7955c8b64ce6591de3b3f64
Refs 1721

Test Failures


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

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:453
Timed out after 1200.001s.
System machine pools not ready
Expected
    <bool>: false
to equal
    <bool>: true
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/aks.go:216
				
				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 430 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:453

INFO: "with a single control plane node and 1 node" started at Fri, 15 Oct 2021 12:57:21 UTC on Ginkgo node 1 of 3
STEP: Creating namespace "capz-e2e-8f1zbm" for hosting the cluster
Oct 15 12:57:21.351: INFO: starting to create namespace for hosting the "capz-e2e-8f1zbm" test spec
2021/10/15 12:57:21 failed trying to get namespace (capz-e2e-8f1zbm):namespaces "capz-e2e-8f1zbm" not found
INFO: Creating namespace capz-e2e-8f1zbm
INFO: Creating event watcher for namespace "capz-e2e-8f1zbm"
Oct 15 12:57:21.386: INFO: Creating cluster identity secret
%!(EXTRA string=cluster-identity-secret)INFO: Cluster name is capz-e2e-8f1zbm-aks
INFO: Creating the workload cluster with name "capz-e2e-8f1zbm-aks" using the "aks-multi-tenancy" template (Kubernetes v1.19.13, 1 control-plane machines, 1 worker machines)
INFO: Getting the cluster template yaml
... skipping 104 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:216

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


Ginkgo ran 1 suite in 33m46.03714949s
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
  - For instructions on using the Release Candidate visit https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#using-the-beta
  - To comment, chime in at https://github.com/onsi/ginkgo/issues/711

To silence this notice, set the environment variable: ACK_GINKGO_RC=true
Alternatively you can: touch $HOME/.ack-ginkgo-rc
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 ...