Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1830840

Summary:	[4.4] Wrong bios-type for templates imported from glance server
Product:	[oVirt] ovirt-engine	Reporter:	Beni Pelled <bpelled>
Component:	BLL.Virt	Assignee:	Shmuel Melamud <smelamud>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Beni Pelled <bpelled>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.4.0	CC:	ahadas, bugs, dholler, mavital, michal.skrivanek, mtessun
Target Milestone:	ovirt-4.4.2	Flags:	pm-rhel: ovirt-4.4+ mtessun: planning_ack+ ahadas: devel_ack+ mavital: testing_ack+
Target Release:	4.4.2.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.4.2.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-09-18 07:12:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Beni Pelled 2020-05-04 05:35:44 UTC

Description of problem:
In case of a VM built with q35 and exported to a glance server, after re-import the
template from the glance server, the VM will be with "different" chipset type, which
probably happens mistakenly by some device-changes during the export/import.

Version-Release number of selected component (if applicable):
RHV 4.4.0-0.33.master.el8ev

How reproducible:
100%

Steps to Reproduce:
1. On 4.4 create a VM with q35 as bios type
2. Build a template from this VM
3. Export the template to a glance server
4. Import the exported template as a new template from the glance server
5. Create a new VM from the new imported template

Actual results:
A warning message about 'create a VM from a template with a different chipset' is prompt even that the original VM created with q35

Expected results:
No device-changes OR warning-message about different chipset when the original VM is built with q35

Additional info:

The full warning message: In order to create a VM from a template with a different chipset, device configuration will be changed. This may affect functionality of the guest software. Are you sure you want to proceed?

Comment 1 Michal Skrivanek 2020-06-04 13:14:26 UTC

I believe this is just a message, decresing sev accordingly. 
Or otherwise please describe how the type or devices have changed.

Comment 2 Michal Skrivanek 2020-06-04 13:15:12 UTC

also, please do not open RHV bugs on non-RHV specific issues

Comment 3 Arik 2020-06-07 13:41:16 UTC

Beni, can you please clarify what's the implication of this issue on the automation tests?

Comment 4 Beni Pelled 2020-06-08 13:11:49 UTC

Yes, seems like wrong message only,

No implication (we have automation-issue with EL6 images which I thought was partly due to this bug, but I just found that it's not)
Removing Automation keyword.

Comment 5 Arik 2020-06-08 14:40:55 UTC

*** Bug 1823674 has been marked as a duplicate of this bug. ***

Comment 6 Beni Pelled 2020-08-23 13:45:55 UTC

Verified with:
- ovirt-engine-4.4.2.2-0.3.el8ev.noarch
- libvirt-6.0.0-25.module+el8.2.1+7154+47ffd890.x86_64
- vdsm-4.40.25-1.el8ev.x86_64


Verification steps:
1. Create a VM with q35 as bios type
2. Create a template from the VM
3. Export the template to a glance server
4. Import the exported template as a new template from the glance server
5. Create a new VM from the new imported template


Result:
- VM is created with no warning message about 'different chipset'.

Comment 7 Sandro Bonazzola 2020-09-18 07:12:54 UTC

This bugzilla is included in oVirt 4.4.2 release, published on September 17th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.2 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.