Re-enable capv-on-capa and capv-on-capz tests #557

glitchcrab · 2024-11-25T15:35:08Z

towards https://github.com/giantswarm/giantswarm/issues/32054

Checklist

Update changelog in CHANGELOG.md.

Trigger e2e tests

/run cluster-test-suites

tinkerers-ci · 2024-11-25T16:36:54Z

Oh No! 😱 At least one test suite has failed during the AfterSuite cleanup stage and might have left around some resources on the MC!

Be sure to check the full results in Tekton Dashboard to see which test suite has failed and then run the following on the associated MC to list all leftover resources:

PIPELINE_RUN="pr-cluster-test-suites-557-cluster-test-suites4zbt8"

NAMES="$(kubectl api-resources --verbs list -o name | tr '\n' ,)"
kubectl get "${NAMES:0:${#NAMES}-1}" --show-kind --ignore-not-found -l cicd.giantswarm.io/pipelinerun=${PIPELINE_RUN} -A 2>/dev/null

tinkerers-ci · 2024-11-25T16:37:03Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suites4zbt8`
Commit SHA	`1a5df3d`
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

glitchcrab · 2024-11-25T16:38:32Z

yeah i screwed this - i needed https://github.com/giantswarm/giantswarm-management-clusters/pull/894

glitchcrab · 2024-11-26T12:31:03Z

/run cluster-test-suites TARGET_SUITES=./providers/capv/on-capa/

glitchcrab · 2024-11-26T12:31:26Z

/run cluster-test-suites TARGET_SUITES=./providers/capv/on-capz/

tinkerers-ci · 2024-11-26T13:07:49Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suitesrcfsw`
Commit SHA	`1a5df3d`
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

tinkerers-ci · 2024-11-26T13:22:07Z

Oh No! 😱 At least one test suite has failed during the AfterSuite cleanup stage and might have left around some resources on the MC!

Be sure to check the full results in Tekton Dashboard to see which test suite has failed and then run the following on the associated MC to list all leftover resources:

PIPELINE_RUN="pr-cluster-test-suites-557-cluster-test-suitess47kh"

NAMES="$(kubectl api-resources --verbs list -o name | tr '\n' ,)"
kubectl get "${NAMES:0:${#NAMES}-1}" --show-kind --ignore-not-found -l cicd.giantswarm.io/pipelinerun=${PIPELINE_RUN} -A 2>/dev/null

tinkerers-ci · 2024-11-26T13:22:15Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suitess47kh`
Commit SHA	`1a5df3d`
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

glitchcrab · 2024-11-26T13:37:25Z

/run cluster-test-suites TARGET_SUITES=./providers/capv/on-capa/

tinkerers-ci · 2024-11-26T14:29:00Z

Oh No! 😱 At least one test suite has failed during the AfterSuite cleanup stage and might have left around some resources on the MC!

Be sure to check the full results in Tekton Dashboard to see which test suite has failed and then run the following on the associated MC to list all leftover resources:

PIPELINE_RUN="pr-cluster-test-suites-557-cluster-test-suites8cfn5"

NAMES="$(kubectl api-resources --verbs list -o name | tr '\n' ,)"
kubectl get "${NAMES:0:${#NAMES}-1}" --show-kind --ignore-not-found -l cicd.giantswarm.io/pipelinerun=${PIPELINE_RUN} -A 2>/dev/null

tinkerers-ci · 2024-11-26T14:29:10Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suites8cfn5`
Commit SHA	`1a5df3d`
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

glitchcrab · 2024-11-26T14:48:49Z

/run cluster-test-suites TARGET_SUITES=./providers/capv/on-capa/

tinkerers-ci · 2024-11-26T17:38:59Z

Oh No! 😱 At least one test suite has failed during the AfterSuite cleanup stage and might have left around some resources on the MC!

Be sure to check the full results in Tekton Dashboard to see which test suite has failed and then run the following on the associated MC to list all leftover resources:

PIPELINE_RUN="pr-cluster-test-suites-557-cluster-test-suites48cgb"

NAMES="$(kubectl api-resources --verbs list -o name | tr '\n' ,)"
kubectl get "${NAMES:0:${#NAMES}-1}" --show-kind --ignore-not-found -l cicd.giantswarm.io/pipelinerun=${PIPELINE_RUN} -A 2>/dev/null

tinkerers-ci · 2024-11-26T17:39:07Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suites48cgb`
Commit SHA	`1a5df3d`
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

glitchcrab · 2024-12-02T12:59:15Z

/run cluster-test-suites TARGET_SUITES=./providers/capv/on-capa/

glitchcrab · 2024-12-02T12:59:23Z

/run cluster-test-suites TARGET_SUITES=./providers/capv/on-capz/

glitchcrab · 2024-12-02T13:01:01Z

providers/capv/on-capa/test_data/cluster_values.yaml

+  components:
+    containerd:
+      managementClusterRegistryCache:
+        enabled: false


for the moment we need to disable zot caching for WCs created from CAPA because goat is a private cluster and there is no routing from Neoedge back into the VPC (and hence zot's ingress is inaccessible).

tinkerers-ci · 2024-12-02T13:45:46Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suites2ttdv`
Commit SHA	`1801247`
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

tinkerers-ci · 2024-12-02T13:49:11Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suitescctxn`
Commit SHA	`1801247`
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

glitchcrab · 2024-12-02T13:55:14Z

/run cluster-test-suites TARGET_SUITES=./providers/capv/on-capz/

tinkerers-ci · 2024-12-02T14:31:34Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suitesg5l4t`
Commit SHA	`1801247`
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

glitchcrab · 2024-12-13T17:02:22Z

/run cluster-test-suites TARGET_SUITES=./providers/capv/on-capa/

tinkerers-ci · 2024-12-13T17:22:43Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suitesdsfmk`
Commit SHA	`1801247`
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

glitchcrab · 2024-12-13T21:54:43Z

/run cluster-test-suites TARGET_SUITES=./providers/capv/on-capa/

tinkerers-ci · 2024-12-13T22:15:05Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suites7zchv`
Commit SHA	`1801247`
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

glitchcrab · 2024-12-14T10:29:45Z

/run cluster-test-suites TARGET_SUITES=./providers/capv/on-capa/

tinkerers-ci · 2024-12-14T10:50:05Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suitesqvf5v`
Commit SHA	`1801247`
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

glitchcrab · 2024-12-16T09:52:42Z

/run cluster-test-suites TARGET_SUITES=./providers/capv/on-capa/

tinkerers-ci · 2024-12-16T10:13:06Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suitesclztd`
Commit SHA	`1801247`
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

glitchcrab · 2024-12-16T11:38:03Z

/run cluster-test-suites TARGET_SUITES=./providers/capv/on-capa/

tinkerers-ci · 2024-12-16T12:27:42Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suiteswhxk8`
Commit SHA	`7419f99`
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

glitchcrab · 2024-12-16T14:35:12Z

let's try azure

/run cluster-test-suites TARGET_SUITES=./providers/capv/on-capz/

glitchcrab · 2024-12-16T14:57:48Z

/run cluster-test-suites TARGET_SUITES=./providers/capv/on-capz/

tinkerers-ci · 2024-12-16T15:09:24Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suitesbswkr`
Commit SHA	`7419f99`
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

tinkerers-ci · 2024-12-16T15:28:23Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suites998nl`
Commit SHA	`7419f99`
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

glitchcrab · 2024-12-16T15:29:20Z

ok routing is fixed for azure:

/run cluster-test-suites TARGET_SUITES=./providers/capv/on-capz/

tinkerers-ci · 2024-12-16T15:59:38Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suitesgq4lx`
Commit SHA	`7419f99`
Result	Completed ✅

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

glitchcrab · 2024-12-17T16:02:59Z

/run cluster-test-suites TARGET_SUITES=./providers/capv/on-capa/

tinkerers-ci · 2024-12-17T16:29:46Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suitessnxv6`
Commit SHA	`7419f99`
Result	Completed ✅

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

This reverts commit 7419f99.

This reverts commit 764d4bd.

glitchcrab · 2024-12-17T16:31:54Z

/run cluster-test-suites TARGET_SUITES=./providers/capv/on-capa/

glitchcrab · 2024-12-17T16:32:00Z

/run cluster-test-suites TARGET_SUITES=./providers/capv/on-capz/

tinkerers-ci · 2024-12-17T17:17:27Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suitestdcsf`
Commit SHA	`f9c8c8d`
Result	Completed ✅

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

tinkerers-ci · 2024-12-17T17:19:46Z

cluster-test-suites

Run name	`pr-cluster-test-suites-557-cluster-test-suitesggfqz`
Commit SHA	`f9c8c8d`
Result	Completed ✅

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

glitchcrab requested review from a team as code owners November 25, 2024 15:35

glitchcrab self-assigned this Nov 25, 2024

AverageMarcus approved these changes Nov 25, 2024

View reviewed changes

glitchcrab commented Dec 2, 2024

View reviewed changes

glitchcrab added 3 commits December 16, 2024 11:37

Re-enable capv-on-capa and capv-on-capz tests

3ff1fcf

disable zot for vSphere WCs created from CAPA

764d4bd

disable zot for vSphere WCs created from CAPZ

7419f99

glitchcrab force-pushed the re-enable-capv-cloud branch from 73cf39a to 7419f99 Compare December 16, 2024 11:37

anvddriesch approved these changes Dec 17, 2024

View reviewed changes

glitchcrab added 2 commits December 17, 2024 16:30

Revert "disable zot for vSphere WCs created from CAPZ"

579da3d

This reverts commit 7419f99.

Revert "disable zot for vSphere WCs created from CAPA"

f9c8c8d

This reverts commit 764d4bd.

Merge branch 'main' into re-enable-capv-cloud

fa26078

glitchcrab merged commit 295d4eb into main Dec 17, 2024
1 of 3 checks passed

glitchcrab deleted the re-enable-capv-cloud branch December 17, 2024 18:02

Re-enable capv-on-capa and capv-on-capz tests #557

Re-enable capv-on-capa and capv-on-capz tests #557

Conversation

glitchcrab commented Nov 25, 2024

Checklist

Trigger e2e tests

tinkerers-ci bot commented Nov 25, 2024

tinkerers-ci bot commented Nov 25, 2024

cluster-test-suites

glitchcrab commented Nov 25, 2024

glitchcrab commented Nov 26, 2024

glitchcrab commented Nov 26, 2024

tinkerers-ci bot commented Nov 26, 2024

cluster-test-suites

tinkerers-ci bot commented Nov 26, 2024

tinkerers-ci bot commented Nov 26, 2024

cluster-test-suites

glitchcrab commented Nov 26, 2024

tinkerers-ci bot commented Nov 26, 2024

tinkerers-ci bot commented Nov 26, 2024

cluster-test-suites

glitchcrab commented Nov 26, 2024

tinkerers-ci bot commented Nov 26, 2024

tinkerers-ci bot commented Nov 26, 2024

cluster-test-suites

glitchcrab commented Dec 2, 2024

glitchcrab commented Dec 2, 2024

glitchcrab Dec 2, 2024

Choose a reason for hiding this comment

tinkerers-ci bot commented Dec 2, 2024

cluster-test-suites

tinkerers-ci bot commented Dec 2, 2024

cluster-test-suites

glitchcrab commented Dec 2, 2024

tinkerers-ci bot commented Dec 2, 2024

cluster-test-suites

glitchcrab commented Dec 13, 2024

tinkerers-ci bot commented Dec 13, 2024

cluster-test-suites

glitchcrab commented Dec 13, 2024

tinkerers-ci bot commented Dec 13, 2024

cluster-test-suites

glitchcrab commented Dec 14, 2024

tinkerers-ci bot commented Dec 14, 2024

cluster-test-suites

glitchcrab commented Dec 16, 2024

tinkerers-ci bot commented Dec 16, 2024

cluster-test-suites

glitchcrab commented Dec 16, 2024

tinkerers-ci bot commented Dec 16, 2024

cluster-test-suites

glitchcrab commented Dec 16, 2024

glitchcrab commented Dec 16, 2024

tinkerers-ci bot commented Dec 16, 2024

cluster-test-suites

tinkerers-ci bot commented Dec 16, 2024

cluster-test-suites

glitchcrab commented Dec 16, 2024

tinkerers-ci bot commented Dec 16, 2024

cluster-test-suites

glitchcrab commented Dec 17, 2024

tinkerers-ci bot commented Dec 17, 2024

cluster-test-suites

glitchcrab commented Dec 17, 2024

glitchcrab commented Dec 17, 2024

tinkerers-ci bot commented Dec 17, 2024

cluster-test-suites

tinkerers-ci bot commented Dec 17, 2024

cluster-test-suites