rancher-sandbox/rancher-desktop

E2E failures in CI

Closed this issue · 1 comments

Actual Behavior

We're seeing some occasional E2E failures in CI, especially on pull requests; this is an issue to track the work in looking into it.

Steps to Reproduce

Run CI repeatedly until we hit E2E failures, in both Windows and Linux.

Result

CI failures.

Expected Behavior

No CI failures.

Additional Information

No response

Rancher Desktop Version

main

Rancher Desktop K8s Version

N/A

Which container engine are you using?

containerd (nerdctl)

What operating system are you using?

Ubuntu

Operating System / Build Version

GitHub CI

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

None

Windows User Only

No response

Some relevant logs, possibly from multiple different runs:

2024-12-09T19:33:21.654Z: Updating release version cache with 0 items in cache
2024-12-09T19:33:21.965Z: Got K3s update channel data: stable,latest,testing,v1.16,v1.16-testing,v1.17,v1.17-testing,v1.18,v1.18-testing,v1.19,v1.20,v1.21,v1.22,v1.23,v1.24,v1.25,v1.26,v1.27,v1.28,v1.29,v1.30,v1.31
2024-12-09T19:33:21.965Z: Error: Channel response does not have correct resource type: channel
2024-12-09T19:33:21.965Z: Ignoring failure to get initial versions list: Error: Channel response does not have correct resource type: channel
2024-12-09T19:33:48.978Z: Failed to get k3s version: Error: /home/runner/work/rd/rd/resources/linux/lima/bin/limactl exited with code 127

console.debug(`Got K3s update channel data: ${ channels.data?.map(ch => ch.name) }`);
if (channels.resourceType !== ResourceTypeChannels) {
throw new Error(`Channel response does not have correct resource type: ${ channels.resourceType }`);
}

const ResourceTypeChannels = 'channels';

It looks like the resource type has changed (into singular instead of plural)?