Greetings, all! I just joined up and I'm starting to review the threads. I am running v1.5.1 on 3 Beelink mini pcs and I'm able to create vms via the Harvester UI. I've been able to create a k3s cluster manually and add it to Rancher after it's been created. What I haven't been able to figure out is: how to create a new cluster from the Rancher UI using an openSuse distro. I can start the process in Rancher and Harvester starts to spin up the vms, but it seems to fail/stop without loading up the agent that's needed to talk to Rancher to start installing k3s. I've tried following the docs and a bunch of YouTube videos, but they all seem to be for older versions of Harvester and openSuse. I can't seem to find any that talk about using MicroOS from Rancher. Any info you could provide would be greatly appreciated!

Its very helpful to pinpoint the failing/erroring pod (most of the time there is something failing when it doesn't work) and see the actual error.

I'm not looking for help with a specific error, because there isn't one. The status is stuck at: Waiting for agent check in - or something like that. What I'm asking is if someone has instructions for the process to create a new VM on Harvester using the Rancher UI and an openSuse distro. A bunch of the older videos use Ubuntu, but I'd like to do it all with Suse, if possible. Most of the videos are at least 2 years old now. I had some partial success trying to use the advanced tab and cloud config templates, but not 100%.

Does it work for you when you use ubuntu image?

Last time I tried, it did not. I saw that v 1.6 has dropped. I think I'm going to start from scratch. Not worry about using my local dns and CA and see if I can get things working with just ip addresses. Very frustrating because Rancher and Harvester seem to be working fine on their own, just not well together.

I just have them working together yesterday.. well almost, because ssh into the node from Rancher doesnt work for some reason. Using ubuntu cloud image. The network part (VLAN/DHCP and NAT/Firewal rules) was a very bumpy ride for me, but I'm learning (a lot) as I go..

Are you doing anything with the cloud image yaml files or just sticking with default values?

The test cluster that I deployed from Rancher received only configuration from the Rancher UI (resources, network and volumes), didn't use any yaml files.

Thanks for the feedback. Sorry for the delayed response, I got sick and took a bit of a mental health break. I ended up creating a new k3s cluster and installing Rancher on it using it's own self-signed certs. I'm pretty much back to where I was before. Rancher creates the new vms in Harvester (using ubuntu minimal 24). Harvester created all 3 and they were showing as running, but only 1 ended up with an IP address. Rancher killed the other two after awhile and created two more. The one that seemed to get to the next step has a Reconciling status in Rancher with the message that it's waiting for the agent to check in. Any suggestions on what I can look at to see why it's not completing?

If you able to create 3 VM's manually in Harvester and they all are getting IP's - check your Harvester/VM to Rancher connectivity maybe.