Itxaka

> @Itxaka Anyway, I should be able to give you access to the runner tomorrow, I just have to prepare it 20 minutes before. > > I see this message...

Lets do some debug steps first: - Install rancher with debug=on - Install the operator with debug=on Then lets check when the upgrade was created (timestamp) and wait for it...

``` diff --git a/tests/e2e/install_test.go b/tests/e2e/install_test.go index 29c7c93..50331a5 100644 --- a/tests/e2e/install_test.go +++ b/tests/e2e/install_test.go @@ -120,6 +120,7 @@ var _ = Describe("E2E - Install Rancher", Label("install"), func() { "--set", "extraEnv[2].value=https://releases.rancher.com/dashboard/"+uiVersion+"/index.html", "--set", "extraEnv[3].name=CATTLE_UI_OFFLINE_PREFERRED",...

Maybe we should set the k3s to debug as well to see what is going on during that 20 minute hole?

umm, on the rancher side at 11:05:46 you can se a PATCH call to the elemental cluster that sets the Ready to false: ``` { "kind": "Cluster", "apiVersion": "cluster.x-k8s.io/v1beta1", "metadata":...

the k3s.log on from elemental-support only has logs up to 11:00? Also, could you get the logs from teh `system-upgrade-controller` ? somehow the support binary doesnt get the pods logs...

awesome, love the fonts, seems much nicer than the usual diagrams! The only issue I can see is that there are no numbers, so its a bit confusing what comes...

under the elemental-operator there are actions that have no support yet for the deprecations: - setup-kind has no updates, sent a PR: https://github.com/engineerd/setup-kind/pull/197 - golangci-lint-action also seems to have been...

@davidcassany IMO this should not have a milestone as its not really needed by that date. Nice to have ASAP yes, but not a such closer date. Its a pita...

For elemental-cli: - PR: https://github.com/rancher/elemental-cli/pull/345