Bug 1850103 - OVA exported from oVirt contains InstanceId instead of InstanceID tags
Summary: OVA exported from oVirt contains InstanceId instead of InstanceID tags
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.3.3.6
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ovirt-4.4.1
: ---
Assignee: Arik
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-23 14:38 UTC by shubha
Modified: 2020-07-20 18:50 UTC (History)
4 users (show)

Fixed In Version: rhv-4.4.1-10
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-20 18:50:43 UTC
oVirt Team: Virt
Embargoed:
shubha.kulkarni: needinfo-
pm-rhel: ovirt-4.4+
mtessun: planning_ack+
ahadas: devel_ack+
mavital: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 109850 0 master MERGED change InstanceId to InstanceID in OVFs within OVAs 2020-08-05 06:22:46 UTC

Description shubha 2020-06-23 14:38:44 UTC 
Description of problem:

When vm is exported as OVA, the vm ovf generated has key
<rasd:InstanceId>1</rasd:InstanceId>

 According to
https://www.dmtf.org/sites/default/files/standards/documents/DSP0243_1.1.0.pdf, this should be
<rasd:InstanceID>1</rasd:InstanceID>

This is causing compatibility issues while consuming OVA.

Version-Release number of selected component (if applicable):
4.3.6.6

How reproducible:
Always

Steps to Reproduce:
1. Export OVA from ovirt. 
2. Try to import it to oracle virtualization platform that supports this specification.


Actual results:
Failed to import ova

Expected results:
Import operation should work.

Additional info:
Comment 1 RHEL Program Management 2020-06-24 06:21:03 UTC 
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
Comment 2 Arik 2020-06-24 10:08:58 UTC 
@shubha, could you verify it with:
https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/6524/artifact/check-patch.el8.x86_64/
Comment 3 shubha 2020-06-25 19:06:41 UTC 
Thanks for your quick update! The changes look good. However, I am thinking of adding changes to reader too. I will send some fixes based what we need.
Thanks!!
Comment 4 Nisim Simsolo 2020-07-07 08:16:10 UTC 
Verified:
ovirt-engine-4.4.1.7-0.3.el8ev
vdsm-4.40.22-1.el8ev.x86_64
qemu-kvm-4.2.0-28.module+el8.2.1+7211+16dfe810.x86_64
libvirt-daemon-6.0.0-25.module+el8.2.1+7154+47ffd890.x86_64

Verification scenario:
1. Create new RHEL 8 VM.
2. Export VM as OVA
3. Extract OVA and observe vm.ovf file for 
   Verify:
   rasd:instanceid is now rasd:InstanceID with counters and UUID, for example:
   <rasd:InstanceID>1</rasd:InstanceID>
   <rasd:InstanceID>427d7a39-41b8-4129-ace1-bca3d7d8b6d5</rasd:InstanceID>
4. Import OVA in order to verify there are no regression, verify import succeeded.
5. Run VM and verify VM is running successfully.
Comment 5 Sandro Bonazzola 2020-07-08 08:27:03 UTC 
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Comment 6 shubha 2020-07-20 18:35:54 UTC 
Hello,

I need this fix in 4.3.6.6 branch. Do I need to submit another bugzilla bug to get it back-ported?
Thanks.
Comment 7 Arik 2020-07-20 18:50:43 UTC 
Please don't reopen - this bz was verified on the release it is targeted for.
I'm afraid there's no plan to release another version of 4.3.
Note You need to log in before you can comment on or make changes to this bug.