On Mon, May 23, 2022 at 3:31 PM <upalmin@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@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/PGD6IDKYDEPVFR...