12:04 p.m.
Hi
I would like to migrate VMs from 4.3.10 to 4.4.8 and I tried using Data Domain where i get
this error:
2022-05-19 15:41:06,262+02 ERROR [org.ovirt.engine.core.utils.ovf.OvfManager] (default
task-18) [e0278849-c70a-4cba-8553-b7aac2537314] Error parsing OVF due to OVF error:
Linux8_Clone: cannot read 'rasd:InstanceId' with value: null
Procedure
SOURCE
Log in to the Administration Portal of the source environment.
Shut down all virtual machines running on the required storage domain.
Click Storage → Domains.
Click the storage domain’s name to open the details view.
Click the Data Center tab.
Click Maintenance.
Click OK.
Click Detach, then click OK.
Click Remove.
Click OK to remove the storage domain from the source environment.
DESTINATION
Log in to the Administration Portal of the destination environment.
Click Storage → Domains.
Click Import Domain.
Select the destination data center from the Data Center drop-down list.
Enter a name for the storage domain.
Select the Domain Function and Storage Type from the appropriate drop-down lists.
Select a host from the Host drop-down list.
Enter the details of the storage domain.
Select the Activate Domain in Data Center check box to automatically activate the
storage domain when it is attached.
Click OK.
I would like to migrate VMs from 4.3.10 to 4.4.8 and I tried using Expot Domain where i
get this error:
2022-05-19 19:31:53,083+02 ERROR [org.ovirt.engine.core.utils.ovf.OvfManager] (default
task-18) [975030bb-cc66-409e-9c47-e37049b957df] Error parsing OVF due to OVF error:
icinga2: cannot read 'rasd:InstanceId' with value: null
2022-05-19 19:31:53,085+02 WARN
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-18)
[975030bb-cc66-409e-9c47-e37049b957df] EVENT_ID: IMPORTEXPORT_FAILED_TO_IMPORT_VM(1,168),
Failed to read VM '<UNKNOWN>' OVF, it may be corrupted. Underlying error
message: OVF error: icinga2: cannot read 'rasd:InstanceId' with value: null
Any Ideas?
Regars Uros
10:23 a.m.
New subject: On oVirt 4.4 Can not import VM from Export domain from ovirt-4.3 nor DataDomain from ovirt-4.3
On Sat, May 21, 2022 at 8:53 AM <upalmin(a)gmail.com> wrote:
Hi
I would like to migrate VMs from 4.3.10 to 4.4.8 and I tried using Data Domain where i
get this error:
2022-05-19 15:41:06,262+02 ERROR [org.ovirt.engine.core.utils.ovf.OvfManager] (default
task-18) [e0278849-c70a-4cba-8553-b7aac2537314] Error parsing OVF due to OVF error:
Linux8_Clone: cannot read 'rasd:InstanceId' with value: null
Procedure
SOURCE
Log in to the Administration Portal of the source environment.
Shut down all virtual machines running on the required storage domain.
Click Storage → Domains.
Click the storage domain’s name to open the details view.
Click the Data Center tab.
Click Maintenance.
Click OK.
Click Detach, then click OK.
Click Remove.
Click OK to remove the storage domain from the source environment.
DESTINATION
Log in to the Administration Portal of the destination environment.
Click Storage → Domains.
Click Import Domain.
Select the destination data center from the Data Center drop-down list.
Enter a name for the storage domain.
Select the Domain Function and Storage Type from the appropriate drop-down lists.
Select a host from the Host drop-down list.
Enter the details of the storage domain.
Select the Activate Domain in Data Center check box to automatically activate the
storage domain when it is attached.
Click OK.
I would like to migrate VMs from 4.3.10 to 4.4.8 and I tried using Expot Domain where i
get this error:
2022-05-19 19:31:53,083+02 ERROR [org.ovirt.engine.core.utils.ovf.OvfManager] (default
task-18) [975030bb-cc66-409e-9c47-e37049b957df] Error parsing OVF due to OVF error:
icinga2: cannot read 'rasd:InstanceId' with value: null
2022-05-19 19:31:53,085+02 WARN
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-18)
[975030bb-cc66-409e-9c47-e37049b957df] EVENT_ID: IMPORTEXPORT_FAILED_TO_IMPORT_VM(1,168),
Failed to read VM '<UNKNOWN>' OVF, it may be corrupted. Underlying error
message: OVF error: icinga2: cannot read 'rasd:InstanceId' with value: null
Any Ideas?
Can you share the OVF? The easiest way to find it is probably using
the export domain, the OVF is located in "master/vms/<vm id>/"
Regars Uros
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)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/DVCWG3HWLHU...
3:31 p.m.
New subject: On oVirt 4.4 Can not import VM from Export domain from ovirt-4.3 nor DataDomain from ovirt-4.3
HI
Thank you for fast response.
In the mean time I have discovered what was the problem in my case.
The problem was that export domain and data domain from oVirt 4.3 had OVF where
<InstanceID> tag is used (ID caps letters) instead of expected <InstanceId>.
oVirt 4.4 expected <InstanceId> tag which wasn't used in this case so the
engine assumed that OVF files were corrupted.
Fix for me was simple on Export Domain I swapped InstanceID with InstanceId.
bash# for i in `find . -name "*.ovf"` ; do sudo sed -i
's/InstanceID/InstanceId/g' $i ; done ;
But I could not fix datadomain since I didn't want to dive into OVF_STORE disk. I am
guessing that there is a tool for editing OVF_STORE disks whit out damaging the domain?!
Regards Uros
3:53 p.m.
New subject: On oVirt 4.4 Can not import VM from Export domain from ovirt-4.3 nor DataDomain from ovirt-4.3
On Mon, May 23, 2022 at 3:31 PM <upalmin(a)gmail.com> wrote:
HI
Thank you for fast response.
In the mean time I have discovered what was the problem in my case.
The problem was that export domain and data domain from oVirt 4.3 had OVF where
<InstanceID> tag is used (ID caps letters) instead of expected <InstanceId>.
oVirt 4.4 expected <InstanceId> tag which wasn't used in this case so the
engine assumed that OVF files were corrupted.
Fix for me was simple on Export Domain I swapped InstanceID with InstanceId.
bash# for i in `find . -name "*.ovf"` ; do sudo sed -i
's/InstanceID/InstanceId/g' $i ; done ;
But I could not fix datadomain since I didn't want to dive into OVF_STORE disk. I am
guessing that there is a tool for editing OVF_STORE disks whit out damaging the domain?!
The OVF_STORE disks contains a single tar file at offset 0. You can
extract the tar from the volume
using:
tar xf /path/to/ovf_store/volume
On file storage this is easy - you can modify the contents of the OVF
files in the tar, and write the
modied tar back to the volume, but you must update the size of the tar
in the ovf store metadata file.
For example:
# grep DESCRIPTION
/rhev/data-center/mnt/alpine\:_01/81738a7a-7ca6-43b8-b9d8-1866a1f81f83/images/0b0dd3b2-71a2-4c48-ad83-cea1dc900818/35dd9951-
DESCRIPTION={"Updated":true,"Size":23040,"Last
Updated":"Sun Apr 24
15:46:27 IDT 2022","Storage
Domains":[{"uuid":"81738a7a-7ca6-43b8-b9d8-1866a1f81f83"}],"Disk
Description":"OVF_STORE"}
You need to keep "Size":23040, correct, since engine use it to read
the tar from storage.
On block storage updating the metadata is much harder, so I would not
go in this way.
If the issue is code expecting "InstanceId" but the actual key is
"InstanceID" the right place to
fix this is in the code, accepting "InstanceId" or "InstanceID".
In general this sounds like a bug, so you should file a bug for the
component reading the
OVF (vdsm?).
Nir
10:27 a.m.
New subject: On oVirt 4.4 Can not import VM from Export domain from ovirt-4.3 nor DataDomain from ovirt-4.3
On Mon, May 23, 2022 at 3:31 PM <upalmin(a)gmail.com> wrote:
HI
Thank you for fast response.
In the mean time I have discovered what was the problem in my case.
The problem was that export domain and data domain from oVirt 4.3 had OVF where
<InstanceID> tag is used (ID caps letters) instead of expected <InstanceId>.
That's weird as oVirt 4.3 didn't write InstanceID - that was added in
4.4.1 and only to OVAs [1]
Do you use plain oVirt or a version that may have been patched incorrectly?
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1850103
oVirt 4.4 expected <InstanceId> tag which wasn't used in this case so the
engine assumed that OVF files were corrupted.
Fix for me was simple on Export Domain I swapped InstanceID with InstanceId.
bash# for i in `find . -name "*.ovf"` ; do sudo sed -i
's/InstanceID/InstanceId/g' $i ; done ;
But I could not fix datadomain since I didn't want to dive into OVF_STORE disk. I am
guessing that there is a tool for editing OVF_STORE disks whit out damaging the domain?!
Regards Uros
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)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/PGD6IDKYDEP...
723
days inactive
727
days old
4 comments
3 participants
participants (3)
-
Arik Hadas -
Nir Soffer -
upalmin＠gmail.com