Any idea on this ? It seems that the logins also exist on a 3.4.3 system with FM 1.4.2...
2014-04-24 10:18 GMT+02:00 Matt . <[email protected]>: > I think the same, it tries to relogin after the VM is created and tries to > start it... > > When I cancel the VM in Foreman it stops... > > So the question is, why can Foreman login for create but not login for > start, is there something changed in oVirt for starting VM's ? > > > > > 2014-04-24 10:10 GMT+02:00 Oved Ourfalli <[email protected]>: > > Aren't these the API calls that Foreman does for the provisioning? >> Each API call both logs in at start and logs out when done. >> >> ----- Original Message ----- >> > From: "Itamar Heim" <[email protected]> >> > To: "Matt ." <[email protected]> >> > Cc: "users" <[email protected]>, "Oved Ourfalli" <[email protected]>, >> "Yair Zaslavsky" <[email protected]> >> > Sent: Thursday, April 24, 2014 11:06:44 AM >> > Subject: Re: [ovirt-users] Foreman not starting VM, hangs on finishing >> creating a new VM >> > >> > On 04/24/2014 11:05 AM, Matt . wrote: >> > > Would it be normal that it does this login runs a couple of times per >> > > second ? >> > >> > oved/yair? >> > >> > > >> > > >> > > >> > > >> > > 2014-04-24 7:50 GMT+02:00 Itamar Heim <[email protected] >> > > <mailto:[email protected]>>: >> > > >> > > On 04/23/2014 09:50 PM, Matt . wrote: >> > > >> > > 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 >> > > <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. >> > > >> > > >> > > why do you think above snippet contain an error? >> > > >> > > >> > >> > >> > >
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
