From soeren.malchow at mcon.net Tue May 26 11:36:22 2015 Content-Type: multipart/mixed; boundary="===============0702919425944543575==" MIME-Version: 1.0 From: Soeren Malchow To: users at ovirt.org Subject: [ovirt-users] "metadata not present" Date: Tue, 26 May 2015 15:36:18 +0000 Message-ID: --===============0702919425944543575== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable --_000_D18A5F90CEE6soerenmalchowmconnet_ Content-Type: text/plain; charset=3D"Windows-1252" Content-Transfer-Encoding: quoted-printable 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:= =3D :(wrapper) Unknown libvirterror: ecode: 80 edom: 20 level: 2 message: metad= =3D ata not found: Requested metadata element is not present=3D94 On all cluster servers in the vdsm.log all the time, it seems as if it does= =3D not really hurt, but is this a problem or not and is there something we sh= =3D ould do ? Regards Soeren --_000_D18A5F90CEE6soerenmalchowmconnet_ Content-Type: text/html; charset=3D"Windows-1252" Content-ID: <10F59E5E14C7B34899F10D0A609ECB0C(a)liquidcampaign.com> Content-Transfer-Encoding: quoted-printable
Dear all,

Now i have to ask again, i am getting this

"Thread-7313::DEBUG::2015-05-26 17:34:08,936::libvirtconnection::= =3D 143::root::(wrapper) Unknown libvirterror: ecode: 80 edom: 20 level: 2 mess= =3D age: metadata not found: Requested metadata element is not present=3D94

On all cluster servers in the vdsm.log all the time, it seems as if it= =3D does not really hurt, but is this a problem or not and is there something = =3D we should do ?

Regards
Soeren 
--_000_D18A5F90CEE6soerenmalchowmconnet_-- --===============0702919425944543575== Content-Type: multipart/alternative MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="attachment.bin" LS1fMDAwX0QxOEE1RjkwQ0VFNnNvZXJlbm1hbGNob3dtY29ubmV0XwpDb250ZW50LVR5cGU6IHRl eHQvcGxhaW47IGNoYXJzZXQ9IldpbmRvd3MtMTI1MiIKQ29udGVudC1UcmFuc2Zlci1FbmNvZGlu ZzogcXVvdGVkLXByaW50YWJsZQoKRGVhciBhbGwsCgpOb3cgaSBoYXZlIHRvIGFzayBhZ2Fpbiwg aSBhbSBnZXR0aW5nIHRoaXMKCiJUaHJlYWQtNzMxMzo6REVCVUc6OjIwMTUtMDUtMjYgMTc6MzQ6 MDgsOTM2OjpsaWJ2aXJ0Y29ubmVjdGlvbjo6MTQzOjpyb290Oj0KOih3cmFwcGVyKSBVbmtub3du IGxpYnZpcnRlcnJvcjogZWNvZGU6IDgwIGVkb206IDIwIGxldmVsOiAyIG1lc3NhZ2U6IG1ldGFk PQphdGEgbm90IGZvdW5kOiBSZXF1ZXN0ZWQgbWV0YWRhdGEgZWxlbWVudCBpcyBub3QgcHJlc2Vu dD05NAoKT24gYWxsIGNsdXN0ZXIgc2VydmVycyBpbiB0aGUgdmRzbS5sb2cgYWxsIHRoZSB0aW1l LCBpdCBzZWVtcyBhcyBpZiBpdCBkb2VzPQogbm90IHJlYWxseSBodXJ0LCBidXQgaXMgdGhpcyBh IHByb2JsZW0gb3Igbm90IGFuZCBpcyB0aGVyZSBzb21ldGhpbmcgd2Ugc2g9Cm91bGQgZG8gPwoK UmVnYXJkcwpTb2VyZW4KCi0tXzAwMF9EMThBNUY5MENFRTZzb2VyZW5tYWxjaG93bWNvbm5ldF8K Q29udGVudC1UeXBlOiB0ZXh0L2h0bWw7IGNoYXJzZXQ9IldpbmRvd3MtMTI1MiIKQ29udGVudC1J RDogPDEwRjU5RTVFMTRDN0IzNDg5OUYxMEQwQTYwOUVDQjBDQGxpcXVpZGNhbXBhaWduLmNvbT4K Q29udGVudC1UcmFuc2Zlci1FbmNvZGluZzogcXVvdGVkLXByaW50YWJsZQoKPGh0bWw+CjxoZWFk Pgo8bWV0YSBodHRwLWVxdWl2PTNEIkNvbnRlbnQtVHlwZSIgY29udGVudD0zRCJ0ZXh0L2h0bWw7 IGNoYXJzZXQ9M0RXaW5kb3dzLTE9CjI1MiI+CjwvaGVhZD4KPGJvZHkgc3R5bGU9M0Qid29yZC13 cmFwOiBicmVhay13b3JkOyAtd2Via2l0LW5ic3AtbW9kZTogc3BhY2U7IC13ZWJraXQtbGluPQpl LWJyZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXpl OiAxNHB4OyBmb250LWZhbWk9Cmx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyI+CjxkaXY+RGVhciBh bGwsPC9kaXY+CjxkaXY+PGJyPgo8L2Rpdj4KPGRpdj5Ob3cgaSBoYXZlIHRvIGFzayBhZ2Fpbiwg aSBhbSBnZXR0aW5nIHRoaXM8L2Rpdj4KPGRpdj48YnI+CjwvZGl2Pgo8ZGl2PiZxdW90O1RocmVh ZC03MzEzOjpERUJVRzo6MjAxNS0wNS0yNiAxNzozNDowOCw5MzY6OmxpYnZpcnRjb25uZWN0aW9u Ojo9CjE0Mzo6cm9vdDo6KHdyYXBwZXIpIFVua25vd24gbGlidmlydGVycm9yOiBlY29kZTogODAg ZWRvbTogMjAgbGV2ZWw6IDIgbWVzcz0KYWdlOiBtZXRhZGF0YSBub3QgZm91bmQ6IFJlcXVlc3Rl ZCBtZXRhZGF0YSBlbGVtZW50IGlzIG5vdCBwcmVzZW50PTk0PC9kaXY+CjxkaXY+PGJyPgo8L2Rp dj4KPGRpdj5PbiBhbGwgY2x1c3RlciBzZXJ2ZXJzIGluIHRoZSB2ZHNtLmxvZyBhbGwgdGhlIHRp bWUsIGl0IHNlZW1zIGFzIGlmIGl0PQogZG9lcyBub3QgcmVhbGx5IGh1cnQsIGJ1dCBpcyB0aGlz IGEgcHJvYmxlbSBvciBub3QgYW5kIGlzIHRoZXJlIHNvbWV0aGluZyA9CndlIHNob3VsZCBkbyA/ PC9kaXY+CjxkaXY+PGJyPgo8L2Rpdj4KPGRpdj5SZWdhcmRzPC9kaXY+CjxkaXY+U29lcmVuJm5i c3A7PC9kaXY+CjwvYm9keT4KPC9odG1sPgoKLS1fMDAwX0QxOEE1RjkwQ0VFNnNvZXJlbm1hbGNo b3dtY29ubmV0Xy0tCg== --===============0702919425944543575==-- From dfediuck at redhat.com Wed May 27 06:19:25 2015 Content-Type: multipart/mixed; boundary="===============0560811887086337582==" MIME-Version: 1.0 From: Doron Fediuck To: users at ovirt.org Subject: Re: [ovirt-users] "metadata not present" Date: Wed, 27 May 2015 13:19:33 +0300 Message-ID: <55659A35.2010504@redhat.com> In-Reply-To: D18A5F90.CEE6%soeren.malchow@mcon.net --===============0560811887086337582== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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=E2=80=9D > = > 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. --===============0560811887086337582==-- From msivak at redhat.com Wed May 27 06:34:08 2015 Content-Type: multipart/mixed; boundary="===============7579483850100947422==" MIME-Version: 1.0 From: Martin Sivak To: users at ovirt.org Subject: Re: [ovirt-users] "metadata not present" Date: Wed, 27 May 2015 06:34:05 -0400 Message-ID: <1215315488.7192633.1432722845206.JavaMail.zimbra@redhat.com> In-Reply-To: 55659A35.2010504@redhat.com --===============7579483850100947422== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable > 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 eve= ry 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 d= id not support metadata. -- Martin Siv=C3=A1k 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=E2=80=9D > > = > > 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. >=20 --===============7579483850100947422==-- From soeren.malchow at mcon.net Wed May 27 09:13:18 2015 Content-Type: multipart/mixed; boundary="===============5844595179523491288==" MIME-Version: 1.0 From: Soeren Malchow To: users at ovirt.org Subject: Re: [ovirt-users] "metadata not present" Date: Wed, 27 May 2015 13:13:14 +0000 Message-ID: In-Reply-To: 1215315488.7192633.1432722845206.JavaMail.zimbra@redhat.com --===============5844595179523491288== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Our installation should not have a mismatch, it is a clean installation of CentOS 7.2 where we only added the ovirt, epel and gluster repos. If I understand this last mail correctly i should be able to set QoS and everythign is fine ? On 27/05/15 12:34, "Martin Sivak" wrote: >> 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=C3=A1k >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=C2=B2 >> > = >> > 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. >> = --===============5844595179523491288==-- From msivak at redhat.com Wed May 27 09:15:12 2015 Content-Type: multipart/mixed; boundary="===============7262398734432959305==" MIME-Version: 1.0 From: Martin Sivak To: users at ovirt.org Subject: Re: [ovirt-users] "metadata not present" Date: Wed, 27 May 2015 09:15:07 -0400 Message-ID: <69217825.7322320.1432732507878.JavaMail.zimbra@redhat.com> In-Reply-To: D18B8D88.D335%soeren.malchow@mcon.net --===============7262398734432959305== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable > If I understand this last mail correctly i should be able to set QoS and > everythign is fine ? Yep, everything should work fine. It is just annoying.. -- Martin Siv=C3=A1k msivak(a)redhat.com Red Hat Czech RHEV-M SLA / Brno, CZ ----- Original Message ----- > Our installation should not have a mismatch, it is a clean installation of > CentOS 7.2 where we only added the ovirt, epel and gluster repos. > = > = > = > On 27/05/15 12:34, "Martin Sivak" wrote: > = > >> 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=C3=A1k > >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 foun= d: > >> > Requested metadata element is not present=C2=B2 > >> > = > >> > 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. > >> = > = >=20 --===============7262398734432959305==-- From michal.skrivanek at redhat.com Wed May 27 09:41:16 2015 Content-Type: multipart/mixed; boundary="===============4805821401563577629==" MIME-Version: 1.0 From: Michal Skrivanek To: users at ovirt.org Subject: Re: [ovirt-users] "metadata not present" Date: Wed, 27 May 2015 15:41:09 +0200 Message-ID: In-Reply-To: 69217825.7322320.1432732507878.JavaMail.zimbra@redhat.com --===============4805821401563577629== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On May 27, 2015, at 15:15 , Martin Sivak wrote: >> If I understand this last mail correctly i should be able to set QoS and >> everythign is fine ? > = > Yep, everything should work fine. It is just annoying.. we didn't fix it? hmm..I thought something fishy is still going on since it's everywhere wher= e i look=E2=80=A6 it's _incredibly_ annoying and IMO must be fixed one way or the other > = > -- > Martin Siv=C3=A1k > msivak(a)redhat.com > Red Hat Czech > RHEV-M SLA / Brno, CZ > = > ----- Original Message ----- >> Our installation should not have a mismatch, it is a clean installation = of >> CentOS 7.2 where we only added the ovirt, epel and gluster repos. >> = > = >> = >> = >> On 27/05/15 12:34, "Martin Sivak" wrote: >> = >>>> 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=C3=A1k >>> 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=C2=B2 >>>>> = >>>>> 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. >>>> = >> = >> = > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users --===============4805821401563577629==--