Bug 1281433 - hostdev_passthrough: VM "spec_params" values are empty in engine DB.
hostdev_passthrough: VM "spec_params" values are empty in engine DB.
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt (Show other bugs)
Unspecified Unspecified
unspecified Severity high (vote)
: ovirt-3.6.1
: 3.6.1
Assigned To: Martin Betak
Nisim Simsolo
Depends On:
  Show dependency treegraph
Reported: 2015-11-12 09:14 EST by Nisim Simsolo
Modified: 2016-02-18 06:10 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-02-18 06:10:51 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Virt
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rule-engine: ovirt‑3.6.z+
mgoldboi: planning_ack+
michal.skrivanek: devel_ack+
mavital: testing_ack+

Attachments (Terms of Use)
engine log (2.31 MB, text/plain)
2015-11-12 09:23 EST, Nisim Simsolo
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 48496 master MERGED backend: Copy host device spec params on template creation Never
oVirt gerrit 48759 ovirt-engine-3.6 MERGED backend: Copy host device spec params on template creation Never

  None (edit)
Description Nisim Simsolo 2015-11-12 09:14:40 EST
Description of problem:
when spec_params value is empty on a VM with attached devices, in some cases the webadmin would not show attached devices under virtul machines tab > attached devices. this means devices cannot be removed from VM.

Version-Release number of selected component (if applicable):
rhevm- (3.6.0-18)

How reproducible:

Steps to Reproduce:
1. Create VM and attach some devices to it.
2. From webadmin, navigate to virtual machines tab > host devices.

Actual results:
In some cases VM host devices list will be empty.
Observing engine DB shows that there are no values for spec_params:
engine=# select spec_params from vm_device where vm_id='26fc68af-6431-4885-aec9-e85720214650';
 { }
 { }
 { }
 { }
   "path" : ""
 { }
 { }
 { }
 { }
 { }
   "heads" : "1",
   "vram" : "32768"
(12 rows)

Expected results:
host devices should be listed.

Additional info:
engine log attached.
Comment 1 Martin Betak 2015-11-12 09:19:08 EST
Nisim: when dumping host devices please restrict the query only to include devices of type 'hostdev' since for other device types empty spec params may be valid state:

select spec_params from vm_device where vm_id='26fc68af-6431-4885-aec9-e85720214650' and type='hostdev';
Comment 2 Nisim Simsolo 2015-11-12 09:23 EST
Created attachment 1093294 [details]
engine log
Comment 3 Red Hat Bugzilla Rules Engine 2015-11-18 09:40:17 EST
Fixed bug tickets must have version flags set prior to fixing them. Please set the correct version flags and move the bugs back to the previous status after this is corrected.
Comment 4 Red Hat Bugzilla Rules Engine 2015-11-18 10:06:19 EST
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 5 Red Hat Bugzilla Rules Engine 2015-11-18 10:06:19 EST
This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset.
Please set the correct milestone or add the z-stream flag.
Comment 6 Eyal Edri 2015-11-29 06:30:01 EST
please make sure to give the bug the right values:

1. bug was fixed before ovirt-3.6.1 1st build was done, therefore if fixed before it should be targeted to the nearest milestone, i.e: ovirt-3.6.1 (otherwise why work on it and not prioritize another 3.6.1 bug?)

2. target release missing - please consult with the ovirt-engine maintainer & builder - in this case Sandro bonzzola and ask on the planned tag for the build,
in this case 'ovirt-engine-3.6.1' - this should be the TR (3.6.1).

3. bug was left on modified, even though it was included in last build, the reason it didn't move to ON_QA is because the milestone was set to a future milestone, please make sure on next releases to verify all the relevant bugs are moved and that are TM & TR are set.

in the build:
Comment 7 Nisim Simsolo 2016-01-25 09:08:10 EST

Verification scenario:
1. Run VM with GPU and host devices attached.
2. Verify no empty "spec_params" values in engine DB:

engine=# select spec_params from vm_device where vm_id='22a0c0b2-06e5-4079-ad0a-a9f42d39d171' and type='hostdev';         spec_params          
   "iommuPlaceholder" : true
   "iommuPlaceholder" : false
   "iommuPlaceholder" : false
   "iommuPlaceholder" : false
(4 rows)


Note You need to log in before you can comment on or make changes to this bug.