importing vm's from storage pool from 4.1.6.2-1 in to 4.4.6 fails due to lingering snapshot configuration in source
I know the subject is a bit wordy but let me try to explain I have a 4.1 installation that I am migrating to 4.4. I placed the storage domain into maintenance and then rsync'ed it to the storage I am using for 4.4. In 4.4 I import the domain and it comes in fine, however, when trying to import some VM's it fails because it says it cannot find a disk. The disk ID's I cannot find anywhere in 4.1 or 4.4 so I opened OVF_STORE after upgrading the pool in 4.4 and look at the ovf file for some of the VM's that are failing to import I see this in the ovf configuration file - <Section xsi:type="ovf:SnapshotsSection_Type"> <Snapshot ovf:id="e300fa3b-eee4-4b96-9103-45115081db57"> <Type>ACTIVE</Type> <Description>Active VM</Description> <CreationDate>2019/12/19 16:47:48</CreationDate> <Memory>07d3447c-c640-4163-9cf1-74ce126d702a,59b5cfdf-015b-0333-004b-000000000397,8c48ea33-dc34-403a-90d2-a3e78776404c,1757809b-9685-4315-a92e-3ea82dc6d8a8,94a2c2b3-e02e-4b05-80eb-6f4b7a9701e7,248a9fd1-61f0-4c5a-b6ab-4630d433c6fa</Memory> </Snapshot> </Section> </Content> </ovf:Envelope> These are the disk ID's I can see failing to import in engine.log I am aware that importing a VM cannot support snapshots and have found multiple mailing list posts around this, however, I do not have any snapshots visible in 4.1 UI. I also tried modifying OVF_STORE by untar'ing it and editing the ovf files directly, however, this does not work as it ends up overwritten by ovirt with the previous configuration Any ideas? As noted, I cannot see any snapshots listed in 4.1 source pool so I therefore cannot remove this stale configuration from the source and upon importing in to 4.4 it fails because it cannot find the disks I tried import partial and that still fails which to me seems like a bug because the idea of the import partial is to still register the VM even if it cant find disks I also tried scanning domain for disks and update OVF's in the UI and it does not help anything -- *Notice to Recipient*: https://www.fixflyer.com/disclaimer <https://www.fixflyer.com/disclaimer>
On Mon, Jun 21, 2021 at 11:45 PM Charles Kozler <charles@fixflyer.com> wrote:
I know the subject is a bit wordy but let me try to explain
I have a 4.1 installation that I am migrating to 4.4. I placed the storage domain into maintenance and then rsync'ed it to the storage I am using for 4.4. In 4.4 I import the domain and it comes in fine, however, when trying to import some VM's it fails because it says it cannot find a disk. The disk ID's I cannot find anywhere in 4.1 or 4.4 so I opened OVF_STORE after upgrading the pool in 4.4 and look at the ovf file for some of the VM's that are failing to import
I see this in the ovf configuration file -
<Section xsi:type="ovf:SnapshotsSection_Type"> <Snapshot ovf:id="e300fa3b-eee4-4b96-9103-45115081db57"> <Type>ACTIVE</Type> <Description>Active VM</Description> <CreationDate>2019/12/19 16:47:48</CreationDate>
<Memory>07d3447c-c640-4163-9cf1-74ce126d702a,59b5cfdf-015b-0333-004b-000000000397,8c48ea33-dc34-403a-90d2-a3e78776404c,1757809b-9685-4315-a92e-3ea82dc6d8a8,94a2c2b3-e02e-4b05-80eb-6f4b7a9701e7,248a9fd1-61f0-4c5a-b6ab-4630d433c6fa</Memory> </Snapshot> </Section> </Content> </ovf:Envelope>
These are the disk ID's I can see failing to import in engine.log
I am aware that importing a VM cannot support snapshots and have found multiple mailing list posts around this, however, I do not have any snapshots visible in 4.1 UI.
I also tried modifying OVF_STORE by untar'ing it and editing the ovf files directly, however, this does not work as it ends up overwritten by ovirt with the previous configuration
Any ideas? As noted, I cannot see any snapshots listed in 4.1 source pool so I therefore cannot remove this stale configuration from the source and upon importing in to 4.4 it fails because it cannot find the disks
I think the only possible explanation to having a VM with no snapshots besides the ACTIVE one and memory attached to the ACTIVE snapshot is that the VM is suspended. In that case, and if the error you get is related to the memory (dump/metadta) disks, shutting down the VM in the source (4.1) env first can solve this
I tried import partial and that still fails which to me seems like a bug because the idea of the import partial is to still register the VM even if it cant find disks
I also tried scanning domain for disks and update OVF's in the UI and it does not help anything
*Notice to Recipient*: https://www.fixflyer.com/disclaimer _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/O4EAECZSGR33FA...
participants (2)
-
Arik Hadas -
Charles Kozler