Re: [ovirt-users] getVdsCapabilites unexpected exception [was: Re: AIO 3.4 on fedora 19 initial errors before coming up]

On Mon, May 12, 2014 at 12:28 PM, Dan Kenigsberg <danken(a)redhat.com&gt; wrote: So, this was I was able to verify on my All-In-One environment based on Fedora 19. 1) yum update python-lxml verified that the only problem was related to python-ethtool and thisn work ok with python-lxml-3.3.5-1.fc19.x86_64 2) update vdsmd systemctl stop vdsmd yum localinstall http://resources.ovirt.org/pub/yum-repo/ovirt-release34.rpm yum remove ovirt-release (BTW: nice that 3.4.1 brings in ovirt-3.4-dependencies.repo file and removes (aka renames in .rpmsave) the explicit fedora-virt-preview.repo) yum update vdsm Now vdsm is at vdsm-4.14.8.1-0.fc19.x86_64 systemctl start vdsmd --> ok 3) update python-ethtool and verify new version of vdsm systemctl stop vdsmd yum update python-ethtool Now it is at version python-ethtool-0.9-2.fc19.x86_64 systemctl start vdsmd --> ok vdsClient -s 0 getVdsCaps doesn't return the unexpected exception any more 4) problem with ovirt-engine that apparently doesnt' start after the vdsm update also tried to reboot in this AIO system with only vdsmd updated I got - in engine.log 2014-05-13 00:02:30,480 ERROR [org.ovirt.engine.core.dal.dbbroker.generic.DBConfigUtils] (MSC service thread 1-6) Could not parse option AutoRecoveryAllowedTypes value. 2014-05-13 00:02:30,482 INFO [org.ovirt.engine.core.bll.Backend] (MSC service thread 1-6) Running ovirt-engine 3.4.0-1.fc19 - in server.log 2014-05-13 00:02:28,358 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-7) JNDI bindings for session bean named Scheduler in deployment unit subdeployment "scheduler.jar" of deployment "engine.ear" are as follows: java:global/engine/scheduler/Scheduler!org.ovirt.engine.core.utils.timer.SchedulerUtil java:app/scheduler/Scheduler!org.ovirt.engine.core.utils.timer.SchedulerUtil java:module/Scheduler!org.ovirt.engine.core.utils.timer.SchedulerUtil java:global/engine/scheduler/Scheduler java:app/scheduler/Scheduler java:module/Scheduler 2014-05-13 00:02:29,011 ERROR [org.apache.catalina.startup.ContextConfig] (MSC service thread 1-2) Cannot configure an authenticator for method NONE 2014-05-13 00:02:29,011 INFO [org.jboss.web] (MSC service thread 1-8) JBAS018210: Registering web context: /ovirt-engine/services 2014-05-13 00:02:29,014 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: 2014-05-13 00:02:29,012 ERROR [org.jboss.web] (MSC service thread 1-2) JBAS018206: Webapp [/ovirt-engine/api] is unavailable due to startup errors 2014-05-13 00:02:29,015 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Context [/ovirt-engine/api] startup failed due to previous errors 2014-05-13 00:02:29,048 INFO [org.jboss.web] (MSC service thread 1-6) JBAS018210: Registering web context: /api 2014-05-13 00:02:29,120 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.web.deployment.default-host./ovirt-eng ine/api: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./ovirt-engine/api: JBAS018040: Failed to start context at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] .... 2014-05-13 00:05:54,546 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMGetAllTasksInfoVDSCommand] (org.ovirt.thread.pool-6-thread-11) [4356795b] -- executeIrsBrokerCommand: Attempting on storage pool 65c9777e-23f1-4f04-8cea-e7c8871dc88b 2014-05-13 00:05:54,558 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksInfoVDSCommand] (org.ovirt.thread.pool-6-thread-11) [4356795b] START, HSMGetAllTasksInfoVDSCommand(HostName = local_host, HostId = aab9571f-da17-4c3c-9e6b-d0224b84c31e), log id: 3cd3caa0 2014-05-13 00:05:54,565 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksInfoVDSCommand] (org.ovirt.thread.pool-6-thread-11) [4356795b] FINISH, HSMGetAllTasksInfoVDSCommand, return: [], log id: 3cd3caa0 2014-05-13 00:05:54,566 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMGetAllTasksInfoVDSCommand] (org.ovirt.thread.pool-6-thread-11) [4356795b] FINISH, SPMGetAllTasksInfoVDSCommand, return: [], log id: 6e4451df 2014-05-13 00:05:54,566 INFO [org.ovirt.engine.core.bll.AsyncTaskManager] (org.ovirt.thread.pool-6-thread-11) [4356795b] Discovered no tasks on Storage Pool local_datacenter ... 2014-05-13 00:05:59,801 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment ovirt-engine-reports.war in 757ms complete server.log for this part here: https://drive.google.com/file/d/0BwoPbcrMv8mvYllLTUg1eTlhZnc/edit?usp=sha... complete engine.log for this part here: https://drive.google.com/file/d/0BwoPbcrMv8mvWmVuMXF0ZjEzRk0/edit?usp=sha... 5) decided to update to 3.4.1 overall also for the engine part All went ok and smooth, also the dwh and reports part. And I'm able to start and use a Windows Xp vm. Gianluca