--_000_D18A5F90CEE6soerenmalchowmconnet_ Content-Type: text/plain; charset="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:= :(wrapper) Unknown libvirterror: ecode: 80 edom: 20 level: 2 message: metad= ata not found: Requested metadata element is not present=94 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 sh= ould do ? Regards Soeren --_000_D18A5F90CEE6soerenmalchowmconnet_ Content-Type: text/html; charset="Windows-1252" Content-ID: <10F59E5E14C7B34899F10D0A609ECB0C@liquidcampaign.com> Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1= 252"> </head> <body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin= e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami= ly: Calibri, sans-serif;"> <div>Dear all,</div> <div><br> </div> <div>Now i have to ask again, i am getting this</div> <div><br> </div> <div>"Thread-7313::DEBUG::2015-05-26 17:34:08,936::libvirtconnection::= 143::root::(wrapper) Unknown libvirterror: ecode: 80 edom: 20 level: 2 mess= age: metadata not found: Requested metadata element is not present=94</div> <div><br> </div> <div>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 ?</div> <div><br> </div> <div>Regards</div> <div>Soeren </div> </body> </html> --_000_D18A5F90CEE6soerenmalchowmconnet_--
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.
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@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.
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" <msivak@redhat.com> 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ák msivak@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.
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ák msivak@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" <msivak@redhat.com> 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ák msivak@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.
On May 27, 2015, at 15:15 , Martin Sivak <msivak@redhat.com> 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 where i look… it's _incredibly_ annoying and IMO must be fixed one way or the other
-- Martin Sivák msivak@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" <msivak@redhat.com> 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ák msivak@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.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (4)
-
Doron Fediuck -
Martin Sivak -
Michal Skrivanek -
Soeren Malchow