Re: [ovirt-users] Foreman not starting VM, hangs on finishing creating a new VM

Hi All, I'm having an issue with oVirt 3.4 and Foreman 1.5 RC1 at the moment, it does not start/finish a new provisioned VM/Host., it creates it well on oVirt. I'm sure this worked well on a nightly some dags ago and I didn't update it after it. The foreman bug is shown here: http://projects.theforeman.org/issues/5132 What I also see in the engine log is a bunch of admin login errors which I cannot place anywhere: 2014-04-23 20:26:44,203 INFO [org.ovirt.engine.core.bll.LoginUserCommand] (ajp--127.0.0.1-8702-6) Running command: LoginUserCommand internal: false. 2014-04-23 20:26:44,242 INFO [org.ovirt.engine.core.bll.LogoutUserCommand] (ajp--127.0.0.1-8702-6) [2e4a8183] Running command: LogoutUserCommand internal: false. 2014-04-23 20:26:44,276 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp--127.0.0.1-8702-6) [2e4a8183] Correlation ID: 2e4a8183, Call Stack: null, Custom Event ID: -1, Message: User admin logged out. 2014-04-23 20:26:44,470 INFO [org.ovirt.engine.core.bll.LoginUserCommand] (ajp--127.0.0.1-8702-1) Running command: LoginUserCommand internal: false. 2014-04-23 20:26:44,510 INFO [org.ovirt.engine.core.bll.LogoutUserCommand] (ajp--127.0.0.1-8702-1) [5d731a43] Running command: LogoutUserCommand internal: false. 2014-04-23 20:26:44,542 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp--127.0.0.1-8702-1) [5d731a43] Correlation ID: 5d731a43, Call Stack: null, Custom Event ID: -1, Message: User admin logged out. 2014-04-23 20:26:44,575 INFO [org.ovirt.engine.core.bll.LoginUserCommand] (ajp--127.0.0.1-8702-3) Running command: LoginUserCommand internal: false. 2014-04-23 20:26:44,623 INFO [org.ovirt.engine.core.bll.RemoveVmCommand] (ajp--127.0.0.1-8702-3) [708f0b9a] Lock Acquired to object EngineLock [exclusiveLocks= key: 7bfc175c-dbcd-43c9-9549-cde8d3b3b731 value: VM I get the feeling this has something todo with eachother.