1:43 a.m.
Hi Gianluca,
unfortunately you can not connect to SPICE console from moVirt when you have a
spice-proxy
on the way. The reason is that aSPICE (the client we use) does not support SPICE proxy.
So, it is currently not supported - I have opened a bug for it
(https://github.com/matobet/moVirt/issues/188)
to have all info I have looked up now on one place so we can handle it.
thank you for the feedback!
Tomas
----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com>
To: "users" <users(a)ovirt.org>
Sent: Saturday, July 2, 2016 7:35:55 PM
Subject: [ovirt-users] moVirt and spice problem
Hello,
I'm testing moVirt 1.4 on Samsung Note Pro (Android 5.1) to connect through
spice to a self hosted engine configuration with single host, version 3.6.6,
configured with spice proxy (squid)
I can walk through all parts inside the app (always better in new versions,
thanks!) but not the console to vm
mOvirt connection configured as
https://192.168.1.212/ovirt-engine/api
and
ignore certificate checking in advanced settings
In mOvirt I receive, after about one minute when I click "Console":
Unable to connect or authenticate, please check server address, password, and
cert authority and subject.
In engine.log, as I click connect to console in mOvirt I see these lines
2016-07-02 19:23:30,868 INFO [org.ovirt.engine.core.bll.SetVmTicketCommand]
(default task-12) [32908848] Running command: SetVmTicketCommand internal:
false. Entities affected : ID: e9491274-460a-40a1-84bb-503078df9f29 Type:
VMAction group CONNECT_TO_VM with role type USER
2016-07-02 19:23:30,872 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (default
task-12) [32908848] START, SetVmTicketVDSCommand(HostName = hosted_engine_1,
SetVmTicketVDSCommandParameters:{runAsync='true',
hostId='459f6e56-f813-4c73-9950-994a7de8dbb5',
vmId='e9491274-460a-40a1-84bb-503078df9f29', protocol='SPICE',
ticket='X5TDD2OB3FI3', validTime='7200', userName='admin',
userId='0000001a-001a-001a-001a-00000000014f',
disconnectAction='LOCK_SCREEN'}), log id: 507f589b
2016-07-02 19:23:31,891 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (default
task-12) [32908848] FINISH, SetVmTicketVDSCommand, log id: 507f589b
2016-07-02 19:23:31,902 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-12) [32908848] Correlation ID: 32908848, Call Stack: null,
Custom Event ID: -1, Message: User admin@internal initiated console session
for VM f24
no more
I have verified that through web browser, both in user portal and in admin
portal, the user "admin" can connect to f24 VM and open spice connection
going trough squid proxy.
Actually on squid logs I don't see any access when I use mOvirt, so it seems
it doesn't reach it at all...
Actually I think the problem doesn't depend in squid setting and I would have
the problem also without it. It seems problem between tablet and engine
connection
Is there any particular restriction to be able to use spice console with
mOvirt 1.4? For example am I force to use and trust certificate to use spice
console?
Thanks in advance for any help,
Gianluca
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users