Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
q
quaint-alarm-7893
11/08/2022, 5:39 PMDoes anyone have any advice on trying to migrate a vm from Harvester 1.0.3 cluster -> 1.1.0 cluster? i tried backing up a vm from 1.0.3 and adding the same backup store to the 1.1.0 cluster, and it doesnt show up. also tried creating a vm with the same name, and that didnt seem to make the backup show on the new cluster eiether.
g
great-bear-19718
11/08/2022, 10:27 PMthis is a known issue and being tracked: https://github.com/harvester/harvester/issues/3095
we have the fix ready.. and we are trying to get it in v1.1.1
q
quaint-alarm-7893
11/08/2022, 10:28 PM@great-bear-19718 that's great news! i saw the other error about how it doesnt import if the vm doesnt exist in the new cluster. didnt see this issue. thanks! does this fix address the backing image as well?
if not, any suggestions on exporting backing image from 1.0.3 > v1.1.0? (or v1.1.1 for that matter)
g
great-bear-19718
11/08/2022, 10:29 PMit will only allow existing vm backups to be imported into a new cluster
so are you trying to export backing image and then import it in a new cluster?
q
quaint-alarm-7893
11/08/2022, 10:31 PMkind of. i have a v1.0.3 cluster. a lot of my vm's are ports from hyper-v, so there's a backing image from when i exported from hyper-v, converted to qcow, then downloaded into the cluster.
i've noticed that if i take a backup of one of those vms (backing image + changes since i got it up and running in harvester) that the backup is super-small. so i'm assuming the backing image is not part of the vm backup.
so if i backup / restore, i'm still going to run into an issue of getting the backing image from old cluster -> new cluster.
https://github.com/harvester/harvester/issues/3016
here's how i migrated from hyper-v -> harvester if that helps explain my process:
https://github.com/harvester/harvester/issues/2950
g
great-bear-19718
11/08/2022, 10:34 PMthe import can only happen from a http endpoint so when you export the image will need to be made accessible via a http endpoint
we introduced a vm-import-controller in v1.1.0, we do want to add harvester as a source so we can do the migrations from one cluster to another
q
quaint-alarm-7893
11/08/2022, 10:36 PMyeah, i get that, now. but i have a whole slew of images i downloaded into harvester from an http when i was migrating. but as i imported them, i removed them from the server (i had to migrate like 30 vms) so now i have no way of getting them from old cluster to new cluster. does that make sense?
g
great-bear-19718
11/08/2022, 10:36 PMbut i dont have an ETA for it, likely 1.1.2
yeah... makes sense
the best option would be to wait for 1.1.1 and use the nfs backup to repopulate a new cluster
q
quaint-alarm-7893
11/08/2022, 10:37 PMgot ya. but am i right that the backup does not backup the backing image as well?
and if that's the case, any thoughts on how to get that out of cluster A, and into cluster B?
g
great-bear-19718
11/08/2022, 10:38 PMlet me check
q
quaint-alarm-7893
11/08/2022, 10:38 PMp.s. you people are amazing! 😄 i love this project.
g
great-bear-19718
11/08/2022, 10:52 PMi dont have a 1.0.3 cluster running but are you able to access longhorn and see the backing images there?
q
quaint-alarm-7893
11/08/2022, 10:52 PMyes
g
great-bear-19718
11/08/2022, 10:54 PMthen the only option right now may be to download the backing image from longhorn and upload it using the file upload in harvester
q
quaint-alarm-7893
11/08/2022, 10:54 PMi'd be fine w/ that. how do i find it to download?
*in longhorn
g
great-bear-19718
11/08/2022, 10:55 PMthe image name would be the same as the virtualmachineimage name in harvester
if you view yaml of an image you want to export you will see the name in
metadata.namethat will map to $namespace-$imageName in longhorn backing image
q
quaint-alarm-7893
11/08/2022, 10:58 PMokay, so here's an example:
it show's i puled it form that ip, it's obviously no longer available there like we discussed...
so how do i get that out of longhorn?
g
great-bear-19718
11/08/2022, 10:59 PMthat is fine
on the right you should see download option in the menu item
q
quaint-alarm-7893
11/08/2022, 10:59 PMno 😞
just delete and cleanup
(under operation)
g
great-bear-19718
11/08/2022, 11:00 PMaah.. thats what i was trying to check first 😄
it must be pinned to version of LH
q
quaint-alarm-7893
11/08/2022, 11:00 PMyeah. my guess 😞
g
great-bear-19718
11/08/2022, 11:00 PMi will check LH release notes
q
quaint-alarm-7893
11/08/2022, 11:00 PMi really appreciate it!
this is 1.2.4 btw (lh)
g
great-bear-19718
11/08/2022, 11:00 PM👍
that bit i know from harvester release notes 🤣
q
quaint-alarm-7893
11/08/2022, 11:01 PMat least you got me in a direction, i appreciate it.
lol
g
great-bear-19718
11/08/2022, 11:01 PMhttps://github.com/longhorn/longhorn/issues/3155 1.3.0 and higher i'd assume
q
quaint-alarm-7893
11/08/2022, 11:03 PMso i guess i'll have to rifle through lh docs and see if i can figure out how to get an image out of it on older versions.
g
great-bear-19718
11/08/2022, 11:04 PMi will ask internally
q
quaint-alarm-7893
11/08/2022, 11:04 PMi'd almost rather manually move vms from old cluster to new cluster for now, instead of brave an upgrade once they fix the issues... i'm using harvester in prod, so being down for a day or two while working out upgrade bombs would be an issue.
thanks! i appreciate it!
(again)
g
great-bear-19718
11/08/2022, 11:05 PM1.1.1 should be out in a couple of weeks
q
quaint-alarm-7893
11/08/2022, 11:05 PMcareful. you might become my new favorite friend! 🤣
g
great-bear-19718
11/08/2022, 11:05 PMso unless you are waiting for some feature only available in 1.1.x i'd wait
q
quaint-alarm-7893
11/08/2022, 11:05 PMi'm at least waiting for that. for sure.
g
great-bear-19718
11/08/2022, 11:06 PMthen you should be able to upgrade in place and also migrate using backups
q
quaint-alarm-7893
11/08/2022, 11:06 PMand yeah, i want storage classes in 1.1 so bad it hurts!