--_d79ec053-61bc-4ff3-9c0c-b63bebc8d0f5_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello=2C I need a little bit of help to get my setup in a stable state... =3B( I use= d to have this configuration on three physical machines: - engine - oVirt 3.2.1/FC18 - host1 - FC18 - host2 - FC18 - NAS with NFS data domains It all started with my mistake: upgrading the engine to FC19 without checki= ng oVirt compatibility first. Of course=2C afterwards ovirt-engine wouldn't= start anymore=2C but I had my VM's running on the two hosts and I thought = I'd wait it out until 3.3 is released. Today my email server VM crashed and I cannot start it manually (tried vari= ations of the qemu-kvm command line=2C created tap devices=2C tried a few = other things without success). After a while=2C I bit the bullet and enabled the oVirt 3.3 repo=2C and did= engine-upgrade. This seem to have worked fine except for a missing link fo= r Java which I fixed=2C so now I can access the web admin portal. I can see= the hosts and VM's that are running or stopped but I cannot start any VM= =2C error message is: qemu-kvm: -drive file... Permissions denied I checked the path and everything is accessible on the host. Since I didn't have any other critical VM's on one of the host I made possi= bly the second mistake: downloaded the oVirt node ISO and reinstalled from = scratch. First it wouldn't register due to a UUID collision (crappy motherb= oard manufacturers) but I was able to make it report a valid UUID and worke= d around that. When I try to Approve the node=2C it goes through most of the steps but fai= ls with: 2013-08-28 07:37:26 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logSt= ring:215 DIALOG:SEND 2013-08-28 07:37:26 DEBUG otopi.context context.= _executeMethod:119 Stage closeup METHOD otopi.plugins.ovirt_host_deploy.nod= e.persist.Plugin._closeup 2013-08-28 07:37:26 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logSt= ring:215 DIALOG:SEND 2013-08-28 07:37:26 DEBUG otopi.context context.= _executeMethod:133 method exception 2013-08-28 07:37:26 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logSt= ring:215 DIALOG:SEND Traceback (most recent call last): 2013-08-28 07:37:26 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logSt= ring:215 DIALOG:SEND File "/tmp/ovirt-S4pEN1vbH3/pythonlib/otopi/co= ntext.py"=2C line 123=2C in _executeMethod 2013-08-28 07:37:26 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logSt= ring:215 DIALOG:SEND method['method']() 2013-08-28 07:37:26 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logSt= ring:215 DIALOG:SEND File "/tmp/ovirt-S4pEN1vbH3/otopi-plugins/ovir= t-host-deploy/node/persist.py"=2C line 51=2C in _closeup 2013-08-28 07:37:26 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logSt= ring:215 DIALOG:SEND from ovirtnode import ovirtfunctions 2013-08-28 07:37:26 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logSt= ring:215 DIALOG:SEND File "/usr/lib/python2.7/site-packages/ovirtno= de/ovirtfunctions.py"=2C line 34=2C in <module> 2013-08-28 07:37:26 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logSt= ring:215 DIALOG:SEND ImportError: could not import gobject (could not= find _PyGObject_API object) I downgraded the node from 3.1.0-0.999.5.vdsm.fc19 to 3.0.0-5.1.6.vdsm.fc19= but ran into the same error. I noticed the Python scripts being run during the deployment come from ovir= t-host-deploy.tar=2C but I don't know where that comes from. I renamed it a= nd it was recreated. I checked the Python packages and the node does have pygobject2 v2.28.6 ins= talled. Import gobject from Phyton doesn't report any errors and I even tri= ed to run a modified persist.py on the node and it works just fine=2C impor= ts the functions and persists a file I gave it as a parameter. At this point=2C I'm lost=3B the only thing I can think of would be to rein= stall Fedora (FC19?) on the bad node and to try to re-add the node - but I = have a guess I'll see the exact the same error. Or maybe enable the nightly= repo?... Thank you. PS. I set up a temporary mail gateway so I don't lose incoming mail but it'= s getting a lot of spam=2C plus I don't have IMAP access to emails as that = server was doing amavisd spam filtering and IMAP besides Postfix. A way to = start the VM manually on the "good" host would definitely be a workable tem= porary solution. = --_d79ec053-61bc-4ff3-9c0c-b63bebc8d0f5_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <style><!-- .hmmessage P { margin:0px=3B padding:0px } body.hmmessage { font-size: 12pt=3B font-family:Calibri } --></style></head> <body class=3D'hmmessage'><div dir=3D'ltr'>Hello=2C<br><br>I need a little = bit of help to get my setup in a stable state... =3B( I used to have this c= onfiguration on three physical machines:<br>- engine - oVirt 3.2.1/FC18<br>= - host1 - FC18<br>- host2 - FC18<br>- NAS with NFS data domains<br><br>It a= ll started with my mistake: upgrading the engine to FC19 without checking o= Virt compatibility first. Of course=2C afterwards ovirt-engine wouldn't sta= rt anymore=2C but I had my VM's running on the two hosts and I thought I'd = wait it out until 3.3 is released.<br>Today my email server VM crashed and = I cannot start it manually (tried variations of the qemu-kvm command line= =2C created tap&nbsp=3B devices=2C tried a few other things without success= ).<br>After a while=2C I bit the bullet and enabled the oVirt 3.3 repo=2C a= nd did engine-upgrade. This seem to have worked fine except for a missing l= ink for Java which I fixed=2C so now I can access the web admin portal. I c= an see the hosts and VM's that are running or stopped but I cannot start an= y VM=2C error message is:<br><blockquote>qemu-kvm: -drive file... Permissio= ns denied<br></blockquote>I checked the path and everything is accessible o= n the host.<br><br>Since I didn't have any other critical VM's on one of th= e host I made possibly the second mistake: downloaded the oVirt node ISO an= d reinstalled from scratch. First it wouldn't register due to a UUID collis= ion (crappy motherboard manufacturers) but I was able to make it report a v= alid UUID and worked around that.<br>When I try to Approve the node=2C it g= oes through most of the steps but fails with:<br><blockquote><font style=3D= "font-size: 10pt=3B" size=3D"2">2013-08-28 07:37:26 DEBUG otopi.plugins.oto= pi.dialog.machine dialog.__logString:215 DIALOG:SEND&nbsp=3B&nbsp=3B&nbsp= =3B&nbsp=3B&nbsp=3B&nbsp=3B 2013-08-28 07:37:26 DEBUG otopi.context context= ._executeMethod:119 Stage closeup METHOD otopi.plugins.ovirt_host_deploy.no= de.persist.Plugin._closeup</font><br><font style=3D"font-size: 10pt=3B" siz= e=3D"2">2013-08-28 07:37:26 DEBUG otopi.plugins.otopi.dialog.machine dialog= .__logString:215 DIALOG:SEND&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp= =3B 2013-08-28 07:37:26 DEBUG otopi.context context._executeMethod:133 meth= od exception</font><br><font style=3D"font-size: 10pt=3B" size=3D"2">2013-0= 8-28 07:37:26 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:2= 15 DIALOG:SEND&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Traceback (m= ost recent call last):</font><br><font style=3D"font-size: 10pt=3B" size=3D= "2">2013-08-28 07:37:26 DEBUG otopi.plugins.otopi.dialog.machine dialog.__l= ogString:215 DIALOG:SEND&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nb= sp=3B&nbsp=3B File "/tmp/ovirt-S4pEN1vbH3/pythonlib/otopi/context.py"=2C li= ne 123=2C in _executeMethod</font><br><font style=3D"font-size: 10pt=3B" si= ze=3D"2">2013-08-28 07:37:26 DEBUG otopi.plugins.otopi.dialog.machine dialo= g.__logString:215 DIALOG:SEND&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp= =3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B method['method']()</font><br><font styl= e=3D"font-size: 10pt=3B" size=3D"2">2013-08-28 07:37:26 DEBUG otopi.plugins= .otopi.dialog.machine dialog.__logString:215 DIALOG:SEND&nbsp=3B&nbsp=3B&nb= sp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B File "/tmp/ovirt-S4pEN1vbH3/o= topi-plugins/ovirt-host-deploy/node/persist.py"=2C line 51=2C in _closeup</= font><br><font style=3D"font-size: 10pt=3B" size=3D"2">2013-08-28 07:37:26 = DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND= &nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nb= sp=3B from ovirtnode import ovirtfunctions</font><br><font style=3D"font-si= ze: 10pt=3B" size=3D"2">2013-08-28 07:37:26 DEBUG otopi.plugins.otopi.dialo= g.machine dialog.__logString:215 DIALOG:SEND&nbsp=3B&nbsp=3B&nbsp=3B&nbsp= =3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B File "/usr/lib/python2.7/site-packages/= ovirtnode/ovirtfunctions.py"=2C line 34=2C in &lt=3Bmodule&gt=3B</font><br>= <font style=3D"font-size: 10pt=3B" size=3D"2">2013-08-28 07:37:26 DEBUG oto= pi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND&nbsp=3B&= nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B ImportError: could not import gobje= ct (could not find _PyGObject_API object)</font><br></blockquote><br>I down= graded the node from 3.1.0-0.999.5.vdsm.fc19 to 3.0.0-5.1.6.vdsm.fc19 but r= an into the same error.<br>I noticed the Python scripts being run during th= e deployment come from ovirt-host-deploy.tar=2C but I don't know where that= comes from. I renamed it and it was recreated.<br>I checked the Python pac= kages and the node does have pygobject2 v2.28.6 installed. Import gobject f= rom Phyton doesn't report any errors and I even tried to run a modified per= sist.py on the node and it works just fine=2C imports the functions and per= sists a file I gave it as a parameter.<br><br>At this point=2C I'm lost=3B = the only thing I can think of would be to reinstall Fedora (FC19?) on the b= ad node and to try to re-add the node - but I have a guess I'll see the exa= ct the same error. Or maybe enable the nightly repo?...<br><br>Thank you.<b= r><br>PS. I set up a temporary mail gateway so I don't lose incoming mail b= ut it's getting a lot of spam=2C plus I don't have IMAP access to emails as= that server was doing amavisd spam filtering and IMAP besides Postfix. A w= ay to start the VM manually on the "good" host would definitely be a workab= le temporary solution.<br> </div></body> </html>= --_d79ec053-61bc-4ff3-9c0c-b63bebc8d0f5_--