update on setting up rancher single node on a OpenSUSE VM on rancher-users #general

Title

# general

bright-fireman-42144

10/17/2022, 3:08 PM

update on setting up rancher single node on a OpenSUSE VM on harvester (home lab)... unable to retrieve images to deploy an RKE2 cluster on harvester. I thought it was a connectivity issue but I have ensured that both harvester's mgmt/VIP and the OpenSUSE/rancher are in the same VLAN and there is indeed some sort of connectivity between the two but I cannot see .img's pre-staged on harvester and am also getting a "clusters.management.cattle.io "v1" not found" error in Rancher. Any ideas of where to begin troubleshooting?

more info: rancher/rancher:v2.7-head, harvester v1.0.3

agreeable-oil-87482

10/17/2022, 3:16 PM

Don't use

-head

its an experimental build. Stick with one of the supported versions like

bright-fireman-42144

10/17/2022, 3:30 PM

I ran into other issues where -head supposedly included fixes for that shrug, This is just a lab where I am replacing my ESXi host with Harvester so I can mimic a GKE environment so I have zero problems mucking around. which tag would you suggest for rancher/rancher?

agreeable-oil-87482

10/17/2022, 3:32 PM

I usually stick to

:latest

unless there's a specific reason not to, but if you've been told there's a known issue explicitly only fixed in

head

I see why you're using that

bright-fireman-42144

10/17/2022, 3:33 PM

side note: as a VCP, I'm really excited what SUSE (with the Rancher acquisition) is up to... this combination you guys are cobbling together is a real vmware killer!

rancher latest container is constantly restarting on Leap 15.4 which is why I believe I was using the -head release.

attempting to fix the known issue by changing GRUB_CMDLINE_LINUX="cgroup_memory=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=0" as opposed to testing out the new -head release. Will report back later.

it is managing to stay up but still not seeing any images when attempting to use harvester as a cloud to provision RKE2 with Rancher. seeing a bunch of helm errors in the cattle-system ns kubectl get pods -n cattle-system NAME READY STATUS RESTARTS AGE dashboard-shell-mlj75 2/2 Running 0 17m helm-operation-29vrp 1/2 Error 0 37m helm-operation-2lvwx 1/2 Error 0 3m11s helm-operation-4ms85 1/2 Error 0 37m helm-operation-4wtpw 1/2 Error 0 37m helm-operation-5np58 0/2 Error 0 58m helm-operation-5w7ng 0/2 Error 0 58m helm-operation-69cpn 1/2 Error 0 25m helm-operation-8v8j8 1/2 Error 0 17m helm-operation-9b2mn 0/2 Error 0 59m helm-operation-b4xr5 1/2 Error 0 37m helm-operation-bs92m 0/2 Unknown 0 57m helm-operation-cf5z8 0/2 Error 0 50m helm-operation-d92dz 1/2 Error 0 7m14s helm-operation-dcp9s 1/2 Error 0 37m helm-operation-fhn5t 1/2 Error 0 37m helm-operation-flrcm 1/2 Error 0 13m helm-operation-ftl2h 1/2 Error 0 29m helm-operation-fv7ql 0/2 Unknown 0 42m helm-operation-gh2ll 1/2 Error 0 21m helm-operation-h9smr 0/2 Error 0 58m helm-operation-hrgpt 1/2 Error 0 19m helm-operation-jh4pj 1/2 Error 0 70s helm-operation-jj5rm 1/2 Error 0 37m helm-operation-jw87n 1/2 Error 0 37m helm-operation-ks6g6 1/2 Error 0 38m helm-operation-kxflw 1/2 Error 0 33m helm-operation-lscrl 1/2 Error 0 27m helm-operation-lv8ps 0/2 Unknown 0 45m helm-operation-md54k 1/2 Error 0 15m helm-operation-n2729 1/2 Error 0 23m helm-operation-p2mlm 1/2 Error 0 11m helm-operation-q9n48 0/2 Error 0 59m helm-operation-r7hsm 0/2 Unknown 0 55m helm-operation-r9svp 1/2 Error 0 5m13s helm-operation-rgn49 0/2 Error 0 58m helm-operation-s8d6h 1/2 Error 0 9m15s helm-operation-sc72z 0/2 Unknown 0 47m helm-operation-trpng 1/2 Error 0 35m helm-operation-w76ht 1/2 Error 0 31m helm-operation-wtvbt 0/2 Error 0 58m helm-operation-zrm92 0/2 Error 0 58m rancher-webhook-576c5b6859-z5ld4 1/1 Running 8 (39m ago) 75m

8 Views