Re: [ovirt-users] "metadata not present"
this is a symptom of a mismatch with libvirt version.
It will go away once your mom-vdsm and libvirt versions are aligned.
As long as you avoid using QoS you'll be fine.
Actually this is a symptom of no QoS settings. libvirt reports an error every time we
check if there is anything available. There is nothing we can do about this as it has the
same error code as some other important messages.. It does not hurt anything though.
Doron refers to a similar message we used to see when libvirt on CentOS 6 did not support
metadata.
--
Martin Sivák
msivak(a)redhat.com
Red Hat Czech
RHEV-M SLA / Brno, CZ
----- Original Message -----
> On 26/05/15 18:36, Soeren Malchow wrote:
> > Dear all,
> >
> > Now i have to ask again, i am getting this
> >
> > "Thread-7313::DEBUG::2015-05-26
> > 17:34:08,936::libvirtconnection::143::root::(wrapper) Unknown
> > libvirterror: ecode: 80 edom: 20 level: 2 message: metadata not found:
> > Requested metadata element is not present”
> >
> > On all cluster servers in the vdsm.log all the time, it seems as if it
> > does not really hurt, but is this a problem or not and is there
> > something we should do ?
> >
> > Regards
> > Soeren
> >
> >
>
> Hi Soeren,
this is a symptom of a mismatch with libvirt version.
It will go away once your mom-vdsm and libvirt versions are aligned.
>
As long as you avoid using QoS you'll be fine.
>