Scheduled long running test failed - Run ID: 21746970389

[rad-ci-bot]

Bug information

This issue is automatically generated if the scheduled long running test fails. The Radius long running test operates on a schedule of once per day. It's important to understand that the test may fail due to workflow infrastructure issues, like network problems, rather than the flakiness of the test itself. For the further investigation, please visit here.

[brooke-hamilton]

Rad upgrade failure related to errors in the 0.55.0-rc1 release publication pipeline. Fixed in the current RC release.

Target Radius version: 0.55.0-rc1
Running pre-flight checks...
  Running Kubernetes Connectivity...
    ✓ Connected (version: v1.32.10) with sufficient permissions
  Running Helm Connectivity...
Detected upgrade scenario: chart version is 0.55.0-rc1, but using previous deployed version 0.54.0
    ✓ Helm successfully connected to cluster and found Radius release (version: 0.54.0), Contour installed (version: 1.32.0)
  Running Radius Installation...
Detected upgrade scenario: chart version is 0.55.0-rc1, but using previous deployed version 0.54.0
    ✓ Radius is installed (version: 0.54.0), Contour is installed (version: 1.32.0)
  Running Version Compatibility...
    ✓ Upgrade from 0.54.0 to 0.55.0-rc1 is valid
  Running Custom Configuration Validation...
    ✓ No custom configuration parameters provided
  Running Kubernetes Resource Availability...
    ✓ Sufficient resources available for upgrade. Current Radius usage: 0.00 CPU, 570 MB memory. Additional resources needed: 0.00 CPU, 285 MB memory. Available: 54.64 CPU, 218619 MB memory
Pre-flight checks completed successfully
✓ All preflight checks passed
Upgrading Radius from version 0.54.0 to 0.55.0-rc1...
Upgrading Radius...
Error: failed to upgrade Radius: failed to upgrade Radius, err: context deadline exceeded

TraceId:  3753a6a7a06bb4d1a87a5616c2f3afe6