https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# harvester
a
This message was deleted.
b
I could be wrong, but I believe 
1.1.0
has reached end of life.
I bring this up because the Suse folks do a ton of work and I see lots and lots of bug fixes with every single patch. 1.1.0 has been out of support for 2 years now, so who knows what bugs you might be running into at this point.
What did you use as storage for the VMs? Longhorn?
I think you need to use kubectl and get those disks out, (or find them on the host and copy them outside) then re-install and import your images
By disks I mean the longhorn images, not the physical disks they're on.
oof I just realized I might have read what you wrote wrong: > getting a Harvester 1.1.0 install to work Like this might have been around for a while and you're not trying to get a fresh install to work. Sorry if that's the case. 🤦
h
Hi @bland-article-62755, indeed this is an existing Harvester install, with Longhorn as the storage for VMs.
I think I've managed to mount the replicas pvcs
b
Well then sorry for giving you crap about installing old versions
h
No problem man!
b
That's fine if you just need data off the VMs, but the actual qcow/raw images that longhorn uses would be better for importing in the new cluster.
You can bring the VMs back up in their current state that way.
h
Yeah, that would be great, but the thing is that I think that the etcd db is botched too, so when I list the namespaces, I don't see the ones for cattle and longhorn.
I'll try to backup raw data from the VM disks, reinstall Harvester, reinstall VMs and restore the data.
In any case, thanks for your responses!
b
I'd look at the CLI on the nodes themselves and just copy the files out to another box with scp.
Then you can toss the whole thing and wipe it and go straight to 1.3.2.
h
Yes, I'll just do that.
p
Can you list all the pods:
Copy code
kubectl get pods -A
h
Hi Kiefer, yes, I'm getting this:
Copy code
NAMESPACE     NAME                                                    READY   STATUS      RESTARTS       AGE
kube-system   cloud-controller-manager-hera01                         1/1     Running     16 (15h ago)   31h
kube-system   etcd-hera01                                             1/1     Running     7 (15h ago)    31h
kube-system   helm-install-rke2-canal-95wq2                           0/1     Completed   0              17h
kube-system   helm-install-rke2-coredns-9l7kg                         0/1     Completed   0              31h
kube-system   helm-install-rke2-ingress-nginx-7xk2b                   0/1     Completed   0              31h
kube-system   helm-install-rke2-metrics-server-gclkt                  0/1     Completed   0              31h
kube-system   helm-install-rke2-multus-k94zb                          0/1     Completed   0              31h
kube-system   kube-apiserver-hera01                                   1/1     Running     8 (15h ago)    31h
kube-system   kube-controller-manager-hera01                          1/1     Running     16 (15h ago)   31h
kube-system   kube-proxy-hera01                                       1/1     Running     7 (15h ago)    31h
kube-system   kube-scheduler-hera01                                   1/1     Running     8 (15h ago)    31h
kube-system   rke2-canal-4trlz                                        2/2     Running     10 (15h ago)   31h
kube-system   rke2-coredns-rke2-coredns-58fd75f64b-s8msm              1/1     Running     5 (15h ago)    31h
kube-system   rke2-coredns-rke2-coredns-autoscaler-768bfc5985-j8wlq   1/1     Running     5 (15h ago)    31h
kube-system   rke2-ingress-nginx-controller-n6kbs                     1/1     Running     5 (15h ago)    31h
kube-system   rke2-metrics-server-67697454f8-n2zkz                    1/1     Running     5 (15h ago)    31h
kube-system   rke2-multus-ds-qh788                                    1/1     Running     5 (15h ago)    31h
3 Views
Open in Slack
PreviousNext
Powered by