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

Log cluster App status on failure to standup cluster #449

Merged
merged 1 commit into from
Aug 23, 2024

Conversation

AverageMarcus
Copy link
Member

What this PR does

Fixes giantswarm/roadmap#3641

If the BeforeSuite fails we will attempt to grab the status of the cluster App to see if there has been any deployment errors.

Example:

{"level":"info","ts":"2024-08-22T13:55:13+01:00","msg":"Cluster App status: AppVersion='', Version='2.0.0-d7a8852053bca7655bf783c6e820cc85cdc4cc32', ReleaseStatus='deployed', ReleaseReason='', LastDeployed='2024-08-22 13:39:13 +0100 BST'"}

Checklist

  • Update changelog in CHANGELOG.md.

Trigger e2e tests

/run cluster-test-suites

@AverageMarcus AverageMarcus requested review from a team August 23, 2024 07:39
@AverageMarcus AverageMarcus requested review from a team as code owners August 23, 2024 07:39
@AverageMarcus
Copy link
Member Author

Failures are flakes and unrelated to this change.

This change can actually be seen in action in one of the failures:

{"level":"info","ts":"2024-08-23T08:10:14Z","msg":"connection to api-server not yet available - failed to get API group resources: unable to retrieve the complete list of server APIs: v1: Get \"[https://api.t-m6ubf43b4h3ng3qo3v.gaws.gigantic.io:6443/api/v1\](https://api.t-m6ubf43b4h3ng3qo3v.gaws.gigantic.io:6443/api/v1/)": EOF"}
  {"level":"info","ts":"2024-08-23T08:10:24Z","msg":"Attempting to get debug info for Cluster App"}
  {"level":"info","ts":"2024-08-23T08:10:24Z","msg":"Cluster App status: AppVersion='', Version='0.60.0', ReleaseStatus='deployed', ReleaseReason='', LastDeployed='2024-08-23 07:55:10 +0000 UTC'"}
  {"level":"info","ts":"2024-08-23T08:10:24Z","msg":"Getting events for the Cluster App"}
  {"level":"info","ts":"2024-08-23T08:10:24Z","msg":"No events found for Cluster App"}
  [FAILED] in [BeforeSuite] - /go/pkg/mod/github.com/giantswarm/[email protected]/pkg/standup/standup.go:75 @ 08/23/24 08:10:24.829
[BeforeSuite] [FAILED] [1204.110 seconds]

Adding skip label

@AverageMarcus AverageMarcus enabled auto-merge (squash) August 23, 2024 09:15
@AverageMarcus AverageMarcus added the skip/ci Instructs pr-gatekeeper to ignore any required PR checks label Aug 23, 2024
@AverageMarcus AverageMarcus merged commit db4c8e6 into main Aug 23, 2024
3 of 4 checks passed
@AverageMarcus AverageMarcus deleted the debug_standup_failure branch August 23, 2024 09:21
@tinkerers-ci
Copy link

tinkerers-ci bot commented Aug 23, 2024

cluster-test-suites

Run name pr-cluster-test-suites-449-cluster-test-suitesc4mk8
Commit SHA b3c2aed
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip/ci Instructs pr-gatekeeper to ignore any required PR checks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Show App status when e2e tests fail to get the kubeconfig secret
3 participants