Hi Doron,
Thank you for your reply. My problem is it known? It will be corrected in
v3.4?
One solution is it possible now? It's hard to wait few weeks.
Kevin.
2013/12/26 Doron Fediuck <dfediuck(a)redhat.com>
----- Original Message -----
> From: "Kevin Tibi" <kevintibi(a)hotmail.com>
> To: users(a)ovirt.org
> Sent: Thursday, December 26, 2013 3:10:23 PM
> Subject: [Users] Engine as a VM
>
> Hi all,
>
> i try to deploy engine as a VM. I use hosted-engine script. When my
engine is
> up the script failed. I saw ssl error. So i disable SSL on my host (vdsm,
> libvirt, quemu) and on engine. But i have error when i switch host to
> active.
>
> Engine.log :
>
> 2013-12-26 14:09:22,641 INFO
[org.ovirt.engine.core.bll.ActivateVdsCommand]
> (org.ovirt.thread.pool-6-thread-36) [3dcc628e] Activate finished. Lock
> released. Monitoring can run now for host hosted_engine_1 from
data-center
> Default
> 2013-12-26 14:09:22,683 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (org.ovirt.thread.pool-6-thread-36) [3dcc628e] Correlation ID: 3eec943e,
Job
> ID: f88b35fc-5c68-4653-85f5-268a6177c9ad, Call Stack: null, Custom Event
ID:
> -1, Message: Host hosted_engine_1 was activated by admin@internal.
> 2013-12-26 14:09:22,732 INFO
[org.ovirt.engine.core.bll.ActivateVdsCommand]
> (org.ovirt.thread.pool-6-thread-36) [3dcc628e] Lock freed to object
> EngineLock [exclusiveLocks= key: 8dd64eb3-b935-4cc2-8ce8-776f52dd88f3
value:
> VDS
> , sharedLocks= ]
> 2013-12-26 14:05:12,322 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler_Worker-90) Command
> GetCapabilitiesVDSCommand(HostName = hosted_engine_1, HostId =
> 8dd64eb3-b935-4cc2-8ce8-776f52dd88f3, vds=Host[hosted_engine_1])
execution
> failed. Exception: VDSNetworkException: javax.net.ssl.SSLException:
> Unrecognized SSL message, plaintext connection?
>
> Have I forgotten something?
>
> Thx :)
>
> Kevin.
>
>
Hi Kevin,
hosted-engine was not officially released yet, so the current oVirt RPMs
do not include the relevant functionality.
I suggest you wait for oVirt 3.4 in a few weeks, where we should have
it properly built for you.
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users