This job view page is being replaced by Spyglass soon.
Check out the new job view.
Error lines from build-log.txt
... skipping 542 lines ...
INFO: Waiting for the cluster infrastructure to be provisioned
[1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/23/23 05:26:26.693[0m
INFO: Waiting for control plane to be initialized
INFO: Waiting for the first control plane machine managed by capv-e2e-rr6eyo/storage-policy-snod2m to be provisioned
[1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/23/23 05:26:56.756[0m
[38;5;9m[FAILED][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154 [38;5;243m@ 01/23/23 05:36:56.757[0m
[1mSTEP:[0m Dumping all the Cluster API resources in the "capv-e2e-rr6eyo" namespace [38;5;243m@ 01/23/23 05:36:56.758[0m
[1mSTEP:[0m cleaning up namespace: capv-e2e-rr6eyo [38;5;243m@ 01/23/23 05:36:57.031[0m
[1mSTEP:[0m Deleting cluster storage-policy-snod2m [38;5;243m@ 01/23/23 05:36:57.05[0m
INFO: Waiting for the Cluster capv-e2e-rr6eyo/storage-policy-snod2m to be deleted
[1mSTEP:[0m Waiting for cluster storage-policy-snod2m to be deleted [38;5;243m@ 01/23/23 05:36:57.063[0m
[1mSTEP:[0m Deleting namespace used for hosting test spec [38;5;243m@ 01/23/23 05:37:17.078[0m
INFO: Deleting namespace capv-e2e-rr6eyo
[38;5;9m• [FAILED] [654.806 seconds][0m
[0mCluster creation with storage policy [38;5;9m[1m[It] should create a cluster successfully[0m
[38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-vsphere/test/e2e/storage_policy_test.go:57[0m
[38;5;9m[FAILED] Timed out after 600.000s.
No Control Plane machines came into existence.
Expected
<bool>: false
to be true[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.0/framework/controlplane_helpers.go:154[0m [38;5;243m@ 01/23/23 05:36:56.757[0m
[38;5;243m------------------------------[0m
... skipping 31 lines ...
INFO: Waiting for the cluster infrastructure to be provisioned
[1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/23/23 05:37:18.534[0m
INFO: Waiting for control plane to be initialized
INFO: Waiting for the first control plane machine managed by md-scale-xab9f5/md-scale-gdrbn7 to be provisioned
[1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/23/23 05:38:08.582[0m
[38;5;9m[FAILED][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154 [38;5;243m@ 01/23/23 05:48:08.583[0m
[1mSTEP:[0m Dumping logs from the "md-scale-gdrbn7" workload cluster [38;5;243m@ 01/23/23 05:48:08.583[0m
Failed to get logs for Machine md-scale-gdrbn7-md-0-658ddf5f6f-9vt69, Cluster md-scale-xab9f5/md-scale-gdrbn7: dialing host IP address at : dial tcp :22: connect: connection refused
Failed to get logs for Machine md-scale-gdrbn7-njbtk, Cluster md-scale-xab9f5/md-scale-gdrbn7: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
[1mSTEP:[0m Dumping all the Cluster API resources in the "md-scale-xab9f5" namespace [38;5;243m@ 01/23/23 05:48:10.91[0m
[1mSTEP:[0m Deleting cluster md-scale-xab9f5/md-scale-gdrbn7 [38;5;243m@ 01/23/23 05:48:11.189[0m
[1mSTEP:[0m Deleting cluster md-scale-gdrbn7 [38;5;243m@ 01/23/23 05:48:11.209[0m
INFO: Waiting for the Cluster md-scale-xab9f5/md-scale-gdrbn7 to be deleted
[1mSTEP:[0m Waiting for cluster md-scale-gdrbn7 to be deleted [38;5;243m@ 01/23/23 05:48:11.223[0m
[1mSTEP:[0m Deleting namespace used for hosting the "md-scale" test spec [38;5;243m@ 01/23/23 05:48:31.239[0m
INFO: Deleting namespace md-scale-xab9f5
[38;5;9m• [FAILED] [674.160 seconds][0m
[0mWhen testing MachineDeployment scale out/in [38;5;9m[1m[It] Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count[0m
[38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/md_scale.go:71[0m
[38;5;9m[FAILED] Timed out after 600.000s.
No Control Plane machines came into existence.
Expected
<bool>: false
to be true[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.0/framework/controlplane_helpers.go:154[0m [38;5;243m@ 01/23/23 05:48:08.583[0m
[38;5;243m------------------------------[0m
... skipping 31 lines ...
INFO: Waiting for the cluster infrastructure to be provisioned
[1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/23/23 05:48:32.333[0m
INFO: Waiting for control plane to be initialized
INFO: Waiting for the first control plane machine managed by node-labeling-e2e-q2xe5w/node-labeling-miyocj to be provisioned
[1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/23/23 05:48:52.363[0m
[38;5;9m[FAILED][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154 [38;5;243m@ 01/23/23 05:58:52.364[0m
[1mSTEP:[0m Dumping all the Cluster API resources in the "node-labeling-e2e-q2xe5w" namespace [38;5;243m@ 01/23/23 05:58:52.364[0m
[1mSTEP:[0m cleaning up namespace: node-labeling-e2e-q2xe5w [38;5;243m@ 01/23/23 05:58:52.646[0m
[1mSTEP:[0m Deleting cluster node-labeling-miyocj [38;5;243m@ 01/23/23 05:58:52.663[0m
INFO: Waiting for the Cluster node-labeling-e2e-q2xe5w/node-labeling-miyocj to be deleted
[1mSTEP:[0m Waiting for cluster node-labeling-miyocj to be deleted [38;5;243m@ 01/23/23 05:58:52.676[0m
[1mSTEP:[0m Deleting namespace used for hosting test spec [38;5;243m@ 01/23/23 05:59:12.69[0m
INFO: Deleting namespace node-labeling-e2e-q2xe5w
[38;5;9m• [FAILED] [641.450 seconds][0m
[0mLabel nodes with ESXi host info [38;5;9m[1m[It] creates a workload cluster whose nodes have the ESXi host info[0m
[38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-vsphere/test/e2e/node_labeling_test.go:52[0m
[38;5;9m[FAILED] Timed out after 600.000s.
No Control Plane machines came into existence.
Expected
<bool>: false
to be true[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.0/framework/controlplane_helpers.go:154[0m [38;5;243m@ 01/23/23 05:58:52.364[0m
[38;5;243m------------------------------[0m
... skipping 31 lines ...
INFO: Waiting for the cluster infrastructure to be provisioned
[1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/23/23 05:59:13.878[0m
INFO: Waiting for control plane to be initialized
INFO: Waiting for the first control plane machine managed by quick-start-t9eu3q/quick-start-jqfhya-sl7rk to be provisioned
[1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/23/23 05:59:33.933[0m
[38;5;9m[FAILED][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154 [38;5;243m@ 01/23/23 06:09:33.936[0m
[1mSTEP:[0m Dumping logs from the "quick-start-jqfhya" workload cluster [38;5;243m@ 01/23/23 06:09:33.936[0m
Failed to get logs for Machine quick-start-jqfhya-md-0-pkphs-6c6b57c6c4-xlzbl, Cluster quick-start-t9eu3q/quick-start-jqfhya: dialing host IP address at : dial tcp :22: connect: connection refused
Failed to get logs for Machine quick-start-jqfhya-sl7rk-466q9, Cluster quick-start-t9eu3q/quick-start-jqfhya: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
[1mSTEP:[0m Dumping all the Cluster API resources in the "quick-start-t9eu3q" namespace [38;5;243m@ 01/23/23 06:09:36.331[0m
[1mSTEP:[0m Deleting cluster quick-start-t9eu3q/quick-start-jqfhya [38;5;243m@ 01/23/23 06:09:36.61[0m
[1mSTEP:[0m Deleting cluster quick-start-jqfhya [38;5;243m@ 01/23/23 06:09:36.634[0m
INFO: Waiting for the Cluster quick-start-t9eu3q/quick-start-jqfhya to be deleted
[1mSTEP:[0m Waiting for cluster quick-start-jqfhya to be deleted [38;5;243m@ 01/23/23 06:09:36.646[0m
[1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 01/23/23 06:09:56.667[0m
INFO: Deleting namespace quick-start-t9eu3q
[38;5;9m• [FAILED] [643.976 seconds][0m
[0mClusterClass Creation using Cluster API quick-start test [PR-Blocking] [ClusterClass] [38;5;9m[1m[It] Should create a workload cluster[0m
[38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/quick_start.go:78[0m
[38;5;9m[FAILED] Timed out after 600.002s.
No Control Plane machines came into existence.
Expected
<bool>: false
to be true[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.0/framework/controlplane_helpers.go:154[0m [38;5;243m@ 01/23/23 06:09:33.936[0m
[38;5;243m------------------------------[0m
... skipping 39 lines ...
[1mSTEP:[0m Waiting for the control plane to be ready [38;5;243m@ 01/23/23 06:13:18.037[0m
[1mSTEP:[0m Checking all the control plane machines are in the expected failure domains [38;5;243m@ 01/23/23 06:15:48.14[0m
INFO: Waiting for the machine deployments to be provisioned
[1mSTEP:[0m Waiting for the workload nodes to exist [38;5;243m@ 01/23/23 06:15:48.169[0m
[38;5;214m[TIMEDOUT][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/md_rollout.go:71 [38;5;243m@ 01/23/23 06:23:20.914[0m
[1mSTEP:[0m Dumping logs from the "md-rollout-1mrkhg" workload cluster [38;5;243m@ 01/23/23 06:23:20.916[0m
Failed to get logs for Machine md-rollout-1mrkhg-md-0-59f48fbbb4-kspb2, Cluster md-rollout-tcqtrv/md-rollout-1mrkhg: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine md-rollout-1mrkhg-mshft, Cluster md-rollout-tcqtrv/md-rollout-1mrkhg: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
[1mSTEP:[0m Dumping all the Cluster API resources in the "md-rollout-tcqtrv" namespace [38;5;243m@ 01/23/23 06:23:25.077[0m
[1mSTEP:[0m Deleting cluster md-rollout-tcqtrv/md-rollout-1mrkhg [38;5;243m@ 01/23/23 06:23:25.358[0m
[1mSTEP:[0m Deleting cluster md-rollout-1mrkhg [38;5;243m@ 01/23/23 06:23:25.373[0m
INFO: Waiting for the Cluster md-rollout-tcqtrv/md-rollout-1mrkhg to be deleted
[1mSTEP:[0m Waiting for cluster md-rollout-1mrkhg to be deleted [38;5;243m@ 01/23/23 06:23:25.386[0m
[38;5;214m[TIMEDOUT][0m in [AfterEach] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/md_rollout.go:103 [38;5;243m@ 01/23/23 06:23:50.916[0m
... skipping 61 lines ...
| for {
[1m[38;5;214m> select {[0m
| case <-ctx.Done():
| return
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics[0m
[38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225[0m
| }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment))
|
[1m[38;5;214m> go func() {[0m
| defer GinkgoRecover()
| for {
[38;5;214mgoroutine 33202 [sync.Cond.Wait][0m
... skipping 18 lines ...
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc0021bf290, 0x27}, {0xc0021bf2c0, 0x22}, {0xc0021fd280, 0xb}, ...}, ...}, ...)[0m
[38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186[0m
| out := bufio.NewWriter(f)
| defer out.Flush()
[1m[38;5;214m> _, err = out.ReadFrom(podLogs)[0m
| if err != nil && err != io.ErrUnexpectedEOF {
| // Failing to stream logs should not cause the test to fail
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs[0m
[38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161[0m
|
| // Watch each container's logs in a goroutine so we can stream them all concurrently.
[1m[38;5;214m> go func(pod corev1.Pod, container corev1.Container) {[0m
| defer GinkgoRecover()
... skipping 21 lines ...
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc00261e030, 0x28}, {0xc00261e060, 0x23}, {0xc002602884, 0xb}, ...}, ...}, ...)[0m
[38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186[0m
| out := bufio.NewWriter(f)
| defer out.Flush()
[1m[38;5;214m> _, err = out.ReadFrom(podLogs)[0m
| if err != nil && err != io.ErrUnexpectedEOF {
| // Failing to stream logs should not cause the test to fail
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs[0m
[38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161[0m
|
| // Watch each container's logs in a goroutine so we can stream them all concurrently.
[1m[38;5;214m> go func(pod corev1.Pod, container corev1.Container) {[0m
| defer GinkgoRecover()
... skipping 6 lines ...
| for {
[1m[38;5;214m> select {[0m
| case <-ctx.Done():
| return
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics[0m
[38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225[0m
| }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment))
|
[1m[38;5;214m> go func() {[0m
| defer GinkgoRecover()
| for {
[38;5;214mgoroutine 33113 [sync.Cond.Wait][0m
... skipping 18 lines ...
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc00073c7c0, 0x3e}, {0xc00073c800, 0x39}, {0xc0020fda40, 0x21}, ...}, ...}, ...)[0m
[38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186[0m
| out := bufio.NewWriter(f)
| defer out.Flush()
[1m[38;5;214m> _, err = out.ReadFrom(podLogs)[0m
| if err != nil && err != io.ErrUnexpectedEOF {
| // Failing to stream logs should not cause the test to fail
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs[0m
[38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161[0m
|
| // Watch each container's logs in a goroutine so we can stream them all concurrently.
[1m[38;5;214m> go func(pod corev1.Pod, container corev1.Container) {[0m
| defer GinkgoRecover()
... skipping 44 lines ...
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc000d50f00, 0x3a}, {0xc000d50f40, 0x35}, {0xc000f14280, 0x1d}, ...}, ...}, ...)[0m
[38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186[0m
| out := bufio.NewWriter(f)
| defer out.Flush()
[1m[38;5;214m> _, err = out.ReadFrom(podLogs)[0m
| if err != nil && err != io.ErrUnexpectedEOF {
| // Failing to stream logs should not cause the test to fail
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs[0m
[38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161[0m
|
| // Watch each container's logs in a goroutine so we can stream them all concurrently.
[1m[38;5;214m> go func(pod corev1.Pod, container corev1.Container) {[0m
| defer GinkgoRecover()
... skipping 6 lines ...
| for {
[1m[38;5;214m> select {[0m
| case <-ctx.Done():
| return
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics[0m
[38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225[0m
| }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment))
|
[1m[38;5;214m> go func() {[0m
| defer GinkgoRecover()
| for {
[38;5;214mgoroutine 33220 [select][0m
... skipping 3 lines ...
| for {
[1m[38;5;214m> select {[0m
| case <-ctx.Done():
| return
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics[0m
[38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225[0m
| }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment))
|
[1m[38;5;214m> go func() {[0m
| defer GinkgoRecover()
| for {
There were [1m[38;5;9madditional failures[0m detected. To view them in detail run [1mginkgo -vv[0m
... skipping 10 lines ...
[1mSTEP:[0m Cleaning up the vSphere session [38;5;243m@ 01/23/23 06:23:50.923[0m
[1mSTEP:[0m Tearing down the management cluster [38;5;243m@ 01/23/23 06:23:51.09[0m
[38;5;10m[SynchronizedAfterSuite] PASSED [1.624 seconds][0m
[38;5;243m------------------------------[0m
[38;5;9m[1mSummarizing 5 Failures:[0m
[38;5;9m[FAIL][0m [0mCluster creation with storage policy [38;5;9m[1m[It] should create a cluster successfully[0m
[38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154[0m
[38;5;9m[FAIL][0m [0mWhen testing MachineDeployment scale out/in [38;5;9m[1m[It] Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count[0m
[38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154[0m
[38;5;9m[FAIL][0m [0mLabel nodes with ESXi host info [38;5;9m[1m[It] creates a workload cluster whose nodes have the ESXi host info[0m
[38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154[0m
[38;5;9m[FAIL][0m [0mClusterClass Creation using Cluster API quick-start test [PR-Blocking] [ClusterClass] [38;5;9m[1m[It] Should create a workload cluster[0m
[38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154[0m
[38;5;214m[TIMEDOUT][0m [0mClusterAPI Machine Deployment Tests [38;5;243mRunning the MachineDeployment rollout spec [38;5;214m[1m[It] Should successfully upgrade Machines upon changes in relevant MachineDeployment fields[0m
[38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/md_rollout.go:71[0m
[38;5;9m[1mRan 5 of 17 Specs in 3577.878 seconds[0m
[38;5;9m[1mFAIL! - Suite Timeout Elapsed[0m -- [38;5;10m[1m0 Passed[0m | [38;5;9m[1m5 Failed[0m | [38;5;11m[1m1 Pending[0m | [38;5;14m[1m11 Skipped[0m
--- FAIL: TestE2E (3577.88s)
FAIL
Ginkgo ran 1 suite in 1h0m31.719851408s
Test Suite Failed
real 60m31.740s
user 5m32.746s
sys 1m5.129s
make: *** [Makefile:183: e2e] Error 1
Releasing IP claims
ipclaim.ipam.metal3.io "ip-claim-25dacb1e797ff8cd1f3db0432f9301b4bc64f068" deleted
ipclaim.ipam.metal3.io "workload-ip-claim-90924980fb3bceb3190513192a6c901f321b7492" deleted
vpn
WARNING: [capv-prow@cluster-api-provider-vsphere.iam.gserviceaccount.com] appears to be a service account. Service account tokens cannot be revoked, but they will expire automatically. To prevent use of the service account token earlier than the expiration, delete or disable the parent service account. To explicitly delete the key associated with the service account use `gcloud iam service-accounts keys delete` instead`.
Revoked credentials:
... skipping 13 lines ...