Bug 1114968

Summary: VDSM keeps reporting QEMU driver does not support <metadata> element
Product: Red Hat Enterprise Virtualization Manager Reporter: Federico Simoncelli <fsimonce>
Component: vdsmAssignee: Martin Sivák <msivak>
Status: CLOSED CURRENTRELEASE QA Contact: Lukas Svaty <lsvaty>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: bazulay, dfediuck, gklein, iheim, lpeer, mavital, ogofen, sherold, yeylon
Target Milestone: ---Keywords: Reopened
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sla
Fixed In Version: vdsm-4.16.6-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-16 13:38:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1156162    

Description Federico Simoncelli 2014-07-01 11:09:05 UTC
Description of problem:
VDSM keeps reporting (vdsm.log) that the QEMU driver does not support <metadata> element:

Thread-143::ERROR::2014-07-01 10:58:33,631::vm::319::vm.Vm::(_sampleCpuTune) vmId=`d4eaecc5-ca2f-4a04-b633-3be7c57ed2c2`::Failed to retrieve QoS metadata
Traceback (most recent call last):
  File "/usr/share/vdsm/virt/vm.py", line 316, in _sampleCpuTune
    libvirt.VIR_DOMAIN_METADATA_ELEMENT, METADATA_VM_TUNE_URI, 0)
  File "/usr/share/vdsm/virt/vm.py", line 604, in f
    ret = attr(*args, **kwargs)
  File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line 111, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 904, in metadata
    if ret is None: raise libvirtError ('virDomainGetMetadata() failed', dom=self)
libvirtError: argument unsupported: QEMU driver does not support <metadata> element

...

Thread-143::ERROR::2014-07-01 10:58:48,652::vm::319::vm.Vm::(_sampleCpuTune) vmId=`d4eaecc5-ca2f-4a04-b633-3be7c57ed2c2`::Failed to retrieve QoS metadata
Traceback (most recent call last):
  File "/usr/share/vdsm/virt/vm.py", line 316, in _sampleCpuTune
    libvirt.VIR_DOMAIN_METADATA_ELEMENT, METADATA_VM_TUNE_URI, 0)
  File "/usr/share/vdsm/virt/vm.py", line 604, in f
    ret = attr(*args, **kwargs)
  File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line 111, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 904, in metadata
    if ret is None: raise libvirtError ('virDomainGetMetadata() failed', dom=self)
libvirtError: argument unsupported: QEMU driver does not support <metadata> element
VM Channels Listener::DEBUG::2014-07-01 10:58:48,794::vmchannels::96::vds::(_handle_timeouts) Timeout on fileno 49.


Version-Release number of selected component (if applicable):
vdsm-4.16.0-7.git15d7b11.el6.x86_64
libvirt-0.10.2-29.el6_5.9.x86_64
qemu-kvm-rhev-0.12.1.2-2.415.el6_5.3.x86_64


How reproducible:
100%

Steps to Reproduce:
1. Start a VM

Actual results:
The error message "QEMU driver does not support <metadata> element" is logged every 15 seconds.

Expected results:
If this is a soft dependency and it's expected that on some platforms the QEMU driver is not supporting <metadata> element, then we should decrease the log verbosity (no traceback, debug/info level, maybe report only once).

Comment 1 Martin Sivák 2014-07-02 10:04:24 UTC

*** This bug has been marked as a duplicate of bug 1115039 ***

Comment 2 Federico Simoncelli 2014-07-02 10:16:18 UTC
(In reply to Martin Sivák from comment #1)
> 
> *** This bug has been marked as a duplicate of bug 1115039 ***

We cannot close the vdsm bug when there's a dependency on another packages to fix the issue.

This bz will be used to track the libvirt spec requirement change in vdsm, e.g.:

-Requires: libvirt >= 1.0.2-1
+Requires: libvirt >= 1.0.x-x

Comment 3 Martin Sivák 2014-07-02 15:32:17 UTC
OK, we decided to add a soft dependency for now so the log is not flooded.

Comment 4 Omer Frenkel 2014-07-08 08:32:59 UTC
*** Bug 1116826 has been marked as a duplicate of this bug. ***

Comment 5 Eyal Edri 2014-10-07 07:16:50 UTC
this bug status was moved to MODIFIED before vdsm vt5 was built,
hence moving to on_qa, if this was mistake and the fix isn't in,
please contact rhev-integ

Comment 6 Lukas Svaty 2014-10-23 10:44:33 UTC
logs seems to be ok in vt7