This message was deleted.
# harvester
a
This message was deleted.
b
There's a scan interval that hits
The
newCluster
has to scan the backup endpoint after the
oldCluster
finishes a completed backup object there.
t
it was 30 minutes and it never showed up.
h
I've asked them to add a manual refresh button, Can you open an issue? It all cant come from me. 😉 Please share the issue number
t
For you, anything. I create one tonight.
h
I doubt we can go back in versions for a restore… let's see!
t
It worked once.. Just not a second time. so confused how to make it work.
I have tried 3 different pcs, 3 different NVME and 2 versions and can’t get pci passthrough to work at all right now. SO BIZARRE. the only thread is that they are all AMD. IT was working for a year and 5 versions. Once upgraded to 1.8.0 the poo hit the fan.
f
1.8.0 has changed the naming of storageclasses
e.g. this is old names: # kubectl get storageclass NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE harvester-longhorn (default) driver.longhorn.io Delete Immediate true 245d longhorn driver.longhorn.io Delete Immediate true 245d longhorn-image-9qpj6 driver.longhorn.io Delete Immediate true 135d longhorn-image-cfftg driver.longhorn.io Delete Immediate true 218d and new names on 1.8.0: # kubectl get storageclasses.storage.k8s.io NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE harvester-longhorn (default) driver.longhorn.io Delete Immediate true 2d13h lh-34d4c111-7c7a-4cd8-aab4-0e94119cb91a driver.longhorn.io Delete Immediate true 42h lh-605f4b8d-ea93-4dde-8bcf-16fabd8da665 driver.longhorn.io Delete Immediate true 10h lh-68cbed1a-4744-408e-ba92-dc611839a947 driver.longhorn.io Delete Immediate true 10h
what I did is created the storage classes matching old names pointing to same vmimages: allowVolumeExpansion: true apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: longhorn-image-pw2m6 parameters: backingImage: vmi-68cbed1a-4744-408e-ba92-dc611839a947 migratable: "true" numberOfReplicas: "3" staleReplicaTimeout: "30" provisioner: driver.longhorn.io reclaimPolicy: Delete volumeBindingMode: Immediate kubectl apply -f ...
🥂 1
and it worked after
t
that did the trick thanks!
And the restores won’t boot.
f
mine worked ok, all guest VMs are Ubuntu with ext4
t
this was user error. I did not have the exact image in place.
b
Been burned by that before. I wish there was a way to flatten the image in the backup so it could restore to any storage class at the block level.
🐿️ 1
p
ZFS does make some things easier 🫣