Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test renovate cloud provider #294

Closed
wants to merge 6 commits into from
Closed

test renovate cloud provider #294

wants to merge 6 commits into from

Conversation

vxav
Copy link
Contributor

@vxav vxav commented Oct 10, 2024

@vxav
Copy link
Contributor Author

vxav commented Oct 10, 2024

/run cluster-test-suites

@tinkerers-ci
Copy link

tinkerers-ci bot commented Oct 10, 2024

cluster-test-suites

Run name pr-cluster-vsphere-294-cluster-test-suitesltqg4
Commit SHA ca77704
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.

@vxav
Copy link
Contributor Author

vxav commented Oct 10, 2024

/run cluster-test-suites

@tinkerers-ci
Copy link

tinkerers-ci bot commented Oct 10, 2024

cluster-test-suites

Run name pr-cluster-vsphere-294-cluster-test-suitestgs4n
Commit SHA ca77704
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.

@vxav
Copy link
Contributor Author

vxav commented Oct 11, 2024

/run cluster-test-suites TARGET_SUITES=./providers/capv/standard

@tinkerers-ci
Copy link

tinkerers-ci bot commented Oct 11, 2024

cluster-test-suites

Run name pr-cluster-vsphere-294-cluster-test-suitesvncc9
Commit SHA ca77704
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.

@vxav vxav marked this pull request as ready for review October 14, 2024 07:24
@vxav vxav requested a review from a team as a code owner October 14, 2024 07:24
@vxav
Copy link
Contributor Author

vxav commented Oct 14, 2024

E2E tests already succeeded, just testing https://gigantic.slack.com/archives/C01BYMF6RN0/p1728887626006229

/run cluster-test-suites TARGET_SUITES=./providers/capv/standard

@tinkerers-ci
Copy link

tinkerers-ci bot commented Oct 14, 2024

cluster-test-suites

Run name pr-cluster-vsphere-294-cluster-test-suitesqldj6
Commit SHA 1dcba00
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.

@vxav
Copy link
Contributor Author

vxav commented Oct 14, 2024

/run cluster-test-suites TARGET_SUITES=./providers/capv/standard

@tinkerers-ci
Copy link

tinkerers-ci bot commented Oct 14, 2024

cluster-test-suites

Run name pr-cluster-vsphere-294-cluster-test-suitesqwth5
Commit SHA 1dcba00
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.

@vxav vxav changed the title Update kubevip helm chart to 0.6.2 test renovate cloud provider Oct 15, 2024
@vxav
Copy link
Contributor Author

vxav commented Oct 15, 2024

/run cluster-test-suites

@tinkerers-ci
Copy link

tinkerers-ci bot commented Oct 15, 2024

cluster-test-suites

Run name pr-cluster-vsphere-294-cluster-test-suites9njkj
Commit SHA 06f6b61
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.

@vxav
Copy link
Contributor Author

vxav commented Oct 15, 2024

/run cluster-test-suites TARGET_SUITES=./providers/capv/standard

@tinkerers-ci
Copy link

tinkerers-ci bot commented Oct 15, 2024

cluster-test-suites

Run name pr-cluster-vsphere-294-cluster-test-suitesxgz58
Commit SHA 06f6b61
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.

@vxav
Copy link
Contributor Author

vxav commented Oct 15, 2024

/run cluster-test-suites

@tinkerers-ci
Copy link

tinkerers-ci bot commented Oct 15, 2024

cluster-test-suites

Run name pr-cluster-vsphere-294-cluster-test-suitesc7856
Commit SHA 59007ac
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.

@vxav
Copy link
Contributor Author

vxav commented Oct 15, 2024

/run cluster-test-suites

@tinkerers-ci
Copy link

tinkerers-ci bot commented Oct 15, 2024

cluster-test-suites

Run name pr-cluster-vsphere-294-cluster-test-suites864w9
Commit SHA 59007ac
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.

Copy link
Contributor

There were differences in the rendered Helm template, please check! ⚠️

Output
=== Differences when rendered with values file helm/cluster-vsphere/ci/test-wc-values.yaml ===

/spec/chart/spec/version  (helm.toolkit.fluxcd.io/v2beta1/HelmRelease/org-giantswarm/release-name-cloud-provider-vsphere)
  ± value change
    - N/A
    + 1.11.0-f7bc7c5e0924e3a32ff0a0d3087da55d889b5a24

/spec/chart/spec/sourceRef/name  (helm.toolkit.fluxcd.io/v2beta1/HelmRelease/org-giantswarm/release-name-cloud-provider-vsphere)
  ± value change
    - release-name-default
    + release-name-default-test

@vxav
Copy link
Contributor Author

vxav commented Oct 15, 2024

/run cluster-test-suites

@tinkerers-ci
Copy link

tinkerers-ci bot commented Oct 15, 2024

cluster-test-suites

Run name pr-cluster-vsphere-294-cluster-test-suites2hwj4
Commit SHA 054bcd8
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.

@vxav
Copy link
Contributor Author

vxav commented Oct 15, 2024

/run cluster-test-suites TARGET_SUITES=./providers/capv/standard

@tinkerers-ci
Copy link

tinkerers-ci bot commented Oct 15, 2024

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-vsphere-294-cluster-test-suitesdn7h6"

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
Copy link

tinkerers-ci bot commented Oct 15, 2024

cluster-test-suites

Run name pr-cluster-vsphere-294-cluster-test-suitesdn7h6
Commit SHA 054bcd8
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.

@Gacko Gacko closed this Oct 23, 2024
@Gacko Gacko deleted the vxav-patch-1 branch October 23, 2024 07:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants