[moVirt] Failed to open console client.
I just started playing with moVirt after I first heard about it here on this list. Wow, that's so much easier to use on my Galaxy S5 than the regular web interface. :-) Of course, now I want the whole bag of chips but can't seem to get the console working. When I press the console button I see "Failed to open console client. Check if aSPICE/bVNC is installed.". I had already installed aSPICE from the Play Store but when that didn't work installed bVNC in addition; still no luck. My engine.log shows this when I try: 2015-03-26 19:52:14,750 INFO [org.ovirt.engine.core.bll.SetVmTicketCommand] (ajp--127.0.0.1-8702-10) [7f6f1f09] Running command: SetVmTicketCommand internal: false. Entities affected : ID: 6ca4e6ae-a201-432b-b22a-2c6517fbd92c Type: VMAction group CONNECT_TO_VM with role type USER 2015-03-26 19:52:14,752 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp--127.0.0.1-8702-10) [7f6f1f09] START, SetVmTicketVDSCommand(HostName = hosted_engine_1, HostId = e90e2ca0-e3b9-46d5-8fde-09fc1c5eed20, vmId=6ca4e6ae-a201-432b-b22a-2c6517fbd92c, ticket=pd2lTiu7w7Ra, validTime=7200,m userName=admin, userId=fdfc627c-d875-11e0-90f0-83df133b58cc), log id: 6257f73 2015-03-26 19:52:14,766 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp--127.0.0.1-8702-10) [7f6f1f09] FINISH, SetVmTicketVDSCommand, log id: 6257f73 2015-03-26 19:52:14,846 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp--127.0.0.1-8702-10) [7f6f1f09] Correlation ID: 7f6f1f09, Call Stack: null, Custom Event ID: -1, Message: user admin@internal initiated console session for VM krypto_f21 What am doing wrong?
Hi, well, consoles are a bit tricky in moVirt. 1: There is a nice chance the stock aSPICE does not work yet and you need a newer version with some patches. You can get it from here: https://github.com/iiordanov/remote-desktop-clients/releases/download/v3.7.7... (maybe it is in play store already but not sure... just try that one please) 2: If this is not the issue there is a nice chance that your hosts are on a different network than your moVirt thus aSPICE /bVNC can not connect. You could verify this by installing some app which is able to ping from phone and try to ping your host from it. If it will not ping them and you don't want to expose the hosts directly, than the consoles are not going to work, because: 1: you could use SPICE PROXY - unfortunately aSPICE does not support it 2: you could use websocket proxy and connect from web clients (SPICE HTML5 or noVNC) - but moVirt does not integrate them since they need a connection to websocket proxy and in order to make a connection to websocket proxy you need a ticket signed by the private certificate of the engine. And the functionality of providing this is not exposed to REST API (only GWT-RPC) so we can not consume it. There is some bug around it and also some work being done around it so I think it will make into 3.6. But 3.6 is far far away... Hope the problem is just old aSPICE :) Tomas ----- John Florian <jflorian@doubledog.org> wrote:
I just started playing with moVirt after I first heard about it here on this list. Wow, that's so much easier to use on my Galaxy S5 than the regular web interface. :-)
Of course, now I want the whole bag of chips but can't seem to get the console working. When I press the console button I see "Failed to open console client. Check if aSPICE/bVNC is installed.". I had already installed aSPICE from the Play Store but when that didn't work installed bVNC in addition; still no luck.
My engine.log shows this when I try:
2015-03-26 19:52:14,750 INFO [org.ovirt.engine.core.bll.SetVmTicketCommand] (ajp--127.0.0.1-8702-10) [7f6f1f09] Running command: SetVmTicketCommand internal: false. Entities affected : ID: 6ca4e6ae-a201-432b-b22a-2c6517fbd92c Type: VMAction group CONNECT_TO_VM with role type USER 2015-03-26 19:52:14,752 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp--127.0.0.1-8702-10) [7f6f1f09] START, SetVmTicketVDSCommand(HostName = hosted_engine_1, HostId = e90e2ca0-e3b9-46d5-8fde-09fc1c5eed20, vmId=6ca4e6ae-a201-432b-b22a-2c6517fbd92c, ticket=pd2lTiu7w7Ra, validTime=7200,m userName=admin, userId=fdfc627c-d875-11e0-90f0-83df133b58cc), log id: 6257f73 2015-03-26 19:52:14,766 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp--127.0.0.1-8702-10) [7f6f1f09] FINISH, SetVmTicketVDSCommand, log id: 6257f73 2015-03-26 19:52:14,846 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp--127.0.0.1-8702-10) [7f6f1f09] Correlation ID: 7f6f1f09, Call Stack: null, Custom Event ID: -1, Message: user admin@internal initiated console session for VM krypto_f21
What am doing wrong? _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
This is a multi-part message in MIME format. --------------070206090605080104060605 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi Tomas, Thanks for the help. Installing the from github as you suggested looks to get me closer. I first uninstalled both aSPICE and bVNC that I'd installed from the play store. It now appears that moVirt is starting aSPICE at least, but now I'm confronted with "Unable to connect or authenticate, please check server address, password and cert authority and subject." Is this because I have moVirt using https for the connection? (I see the moVirt README mentions: *Note* moVirt/aSPICE does not support SPICE secured connections at the moment!) If that's the case, I guess I'll live w/o consoles on my phone for now. I'd rather not send my ovirt admin password in plain-text since that'd be like providing physical access to every one of my critical VMs -- but maybe I'm just interpreting that note wrongly. On 03/27/2015 02:16 AM, Tomas Jelinek wrote:
Hi,
well, consoles are a bit tricky in moVirt.
1: There is a nice chance the stock aSPICE does not work yet and you need a newer version with some patches. You can get it from here: https://github.com/iiordanov/remote-desktop-clients/releases/download/v3.7.7... (maybe it is in play store already but not sure... just try that one please)
2: If this is not the issue there is a nice chance that your hosts are on a different network than your moVirt thus aSPICE /bVNC can not connect. You could verify this by installing some app which is able to ping from phone and try to ping your host from it. If it will not ping them and you don't want to expose the hosts directly, than the consoles are not going to work, because: 1: you could use SPICE PROXY - unfortunately aSPICE does not support it 2: you could use websocket proxy and connect from web clients (SPICE HTML5 or noVNC) - but moVirt does not integrate them since they need a connection to websocket proxy and in order to make a connection to websocket proxy you need a ticket signed by the private certificate of the engine. And the functionality of providing this is not exposed to REST API (only GWT-RPC) so we can not consume it. There is some bug around it and also some work being done around it so I think it will make into 3.6. But 3.6 is far far away...
Hope the problem is just old aSPICE :) Tomas
----- John Florian <jflorian@doubledog.org> wrote:
I just started playing with moVirt after I first heard about it here on this list. Wow, that's so much easier to use on my Galaxy S5 than the regular web interface. :-)
Of course, now I want the whole bag of chips but can't seem to get the console working. When I press the console button I see "Failed to open console client. Check if aSPICE/bVNC is installed.". I had already installed aSPICE from the Play Store but when that didn't work installed bVNC in addition; still no luck.
My engine.log shows this when I try:
2015-03-26 19:52:14,750 INFO [org.ovirt.engine.core.bll.SetVmTicketCommand] (ajp--127.0.0.1-8702-10) [7f6f1f09] Running command: SetVmTicketCommand internal: false. Entities affected : ID: 6ca4e6ae-a201-432b-b22a-2c6517fbd92c Type: VMAction group CONNECT_TO_VM with role type USER 2015-03-26 19:52:14,752 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp--127.0.0.1-8702-10) [7f6f1f09] START, SetVmTicketVDSCommand(HostName = hosted_engine_1, HostId = e90e2ca0-e3b9-46d5-8fde-09fc1c5eed20, vmId=6ca4e6ae-a201-432b-b22a-2c6517fbd92c, ticket=pd2lTiu7w7Ra, validTime=7200,m userName=admin, userId=fdfc627c-d875-11e0-90f0-83df133b58cc), log id: 6257f73 2015-03-26 19:52:14,766 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp--127.0.0.1-8702-10) [7f6f1f09] FINISH, SetVmTicketVDSCommand, log id: 6257f73 2015-03-26 19:52:14,846 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp--127.0.0.1-8702-10) [7f6f1f09] Correlation ID: 7f6f1f09, Call Stack: null, Custom Event ID: -1, Message: user admin@internal initiated console session for VM krypto_f21
What am doing wrong? _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--------------070206090605080104060605 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">Hi Tomas,<br> <br> Thanks for the help. Installing the from github as you suggested looks to get me closer. I first uninstalled both aSPICE and bVNC that I'd installed from the play store. It now appears that moVirt is starting aSPICE at least, but now I'm confronted with "Unable to connect or authenticate, please check server address, password and cert authority and subject." Is this because I have moVirt using https for the connection? (I see the moVirt README mentions: <strong>Note</strong> moVirt/aSPICE does not support SPICE secured connections at the moment!) If that's the case, I guess I'll live w/o consoles on my phone for now. I'd rather not send my ovirt admin password in plain-text since that'd be like providing physical access to every one of my critical VMs -- but maybe I'm just interpreting that note wrongly.<br> <br> On 03/27/2015 02:16 AM, Tomas Jelinek wrote:<br> </div> <blockquote cite="mid:2120695548.5880313.1427436984100.JavaMail.zimbra@redhat.com" type="cite"> <pre wrap="">Hi, well, consoles are a bit tricky in moVirt. 1: There is a nice chance the stock aSPICE does not work yet and you need a newer version with some patches. You can get it from here: <a class="moz-txt-link-freetext" href="https://github.com/iiordanov/remote-desktop-clients/releases/download/v3.7.7/freeaSPICE-3.7.7-final.apk">https://github.com/iiordanov/remote-desktop-clients/releases/download/v3.7.7/freeaSPICE-3.7.7-final.apk</a> (maybe it is in play store already but not sure... just try that one please) 2: If this is not the issue there is a nice chance that your hosts are on a different network than your moVirt thus aSPICE /bVNC can not connect. You could verify this by installing some app which is able to ping from phone and try to ping your host from it. If it will not ping them and you don't want to expose the hosts directly, than the consoles are not going to work, because: 1: you could use SPICE PROXY - unfortunately aSPICE does not support it 2: you could use websocket proxy and connect from web clients (SPICE HTML5 or noVNC) - but moVirt does not integrate them since they need a connection to websocket proxy and in order to make a connection to websocket proxy you need a ticket signed by the private certificate of the engine. And the functionality of providing this is not exposed to REST API (only GWT-RPC) so we can not consume it. There is some bug around it and also some work being done around it so I think it will make into 3.6. But 3.6 is far far away... Hope the problem is just old aSPICE :) Tomas ----- John Florian <a class="moz-txt-link-rfc2396E" href="mailto:jflorian@doubledog.org"><jflorian@doubledog.org></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">I just started playing with moVirt after I first heard about it here on this list. Wow, that's so much easier to use on my Galaxy S5 than the regular web interface. :-) Of course, now I want the whole bag of chips but can't seem to get the console working. When I press the console button I see "Failed to open console client. Check if aSPICE/bVNC is installed.". I had already installed aSPICE from the Play Store but when that didn't work installed bVNC in addition; still no luck. My engine.log shows this when I try: 2015-03-26 19:52:14,750 INFO [org.ovirt.engine.core.bll.SetVmTicketCommand] (ajp--127.0.0.1-8702-10) [7f6f1f09] Running command: SetVmTicketCommand internal: false. Entities affected : ID: 6ca4e6ae-a201-432b-b22a-2c6517fbd92c Type: VMAction group CONNECT_TO_VM with role type USER 2015-03-26 19:52:14,752 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp--127.0.0.1-8702-10) [7f6f1f09] START, SetVmTicketVDSCommand(HostName = hosted_engine_1, HostId = e90e2ca0-e3b9-46d5-8fde-09fc1c5eed20, vmId=6ca4e6ae-a201-432b-b22a-2c6517fbd92c, ticket=pd2lTiu7w7Ra, validTime=7200,m userName=admin, userId=fdfc627c-d875-11e0-90f0-83df133b58cc), log id: 6257f73 2015-03-26 19:52:14,766 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp--127.0.0.1-8702-10) [7f6f1f09] FINISH, SetVmTicketVDSCommand, log id: 6257f73 2015-03-26 19:52:14,846 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp--127.0.0.1-8702-10) [7f6f1f09] Correlation ID: 7f6f1f09, Call Stack: null, Custom Event ID: -1, Message: user admin@internal initiated console session for VM krypto_f21 What am doing wrong? _______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <pre wrap=""> </pre> </blockquote> <br> </body> </html> --------------070206090605080104060605--
----- Original Message -----
From: "John Florian" <jflorian@doubledog.org> To: "Tomas Jelinek" <tjelinek@redhat.com> Cc: users@ovirt.org Sent: Saturday, March 28, 2015 5:07:03 PM Subject: Re: [ovirt-users] [moVirt] Failed to open console client.
Hi Tomas,
Thanks for the help. Installing the from github as you suggested looks to get me closer. I first uninstalled both aSPICE and bVNC that I'd installed from the play store. It now appears that moVirt is starting aSPICE at least, but now I'm confronted with "Unable to connect or authenticate, please check server address, password and cert authority and subject." Is this because I have moVirt using https for the connection? (I see the moVirt README mentions: *Note* moVirt/aSPICE does not support SPICE secured connections at the moment!) If that's the case, I guess I'll live w/o consoles on my phone for now. I'd rather not send my ovirt admin password in plain-text since that'd be like providing physical access to every one of my critical VMs -- but maybe I'm just interpreting that note wrongly.
it seems you are interpreting it correctly - we do not pass the proper certificates to the aSPICE yet. aSPICE should support it, so we just need to get it from engine and pass it. Just need to find some time to actually implement it :)
On 03/27/2015 02:16 AM, Tomas Jelinek wrote:
Hi,
well, consoles are a bit tricky in moVirt.
1: There is a nice chance the stock aSPICE does not work yet and you need a newer version with some patches. You can get it from here: https://github.com/iiordanov/remote-desktop-clients/releases/download/v3.7.7... (maybe it is in play store already but not sure... just try that one please)
2: If this is not the issue there is a nice chance that your hosts are on a different network than your moVirt thus aSPICE /bVNC can not connect. You could verify this by installing some app which is able to ping from phone and try to ping your host from it. If it will not ping them and you don't want to expose the hosts directly, than the consoles are not going to work, because: 1: you could use SPICE PROXY - unfortunately aSPICE does not support it 2: you could use websocket proxy and connect from web clients (SPICE HTML5 or noVNC) - but moVirt does not integrate them since they need a connection to websocket proxy and in order to make a connection to websocket proxy you need a ticket signed by the private certificate of the engine. And the functionality of providing this is not exposed to REST API (only GWT-RPC) so we can not consume it. There is some bug around it and also some work being done around it so I think it will make into 3.6. But 3.6 is far far away...
Hope the problem is just old aSPICE :) Tomas
----- John Florian <jflorian@doubledog.org> wrote:
I just started playing with moVirt after I first heard about it here on this list. Wow, that's so much easier to use on my Galaxy S5 than the regular web interface. :-)
Of course, now I want the whole bag of chips but can't seem to get the console working. When I press the console button I see "Failed to open console client. Check if aSPICE/bVNC is installed.". I had already installed aSPICE from the Play Store but when that didn't work installed bVNC in addition; still no luck.
My engine.log shows this when I try:
2015-03-26 19:52:14,750 INFO [org.ovirt.engine.core.bll.SetVmTicketCommand] (ajp--127.0.0.1-8702-10) [7f6f1f09] Running command: SetVmTicketCommand internal: false. Entities affected : ID: 6ca4e6ae-a201-432b-b22a-2c6517fbd92c Type: VMAction group CONNECT_TO_VM with role type USER 2015-03-26 19:52:14,752 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp--127.0.0.1-8702-10) [7f6f1f09] START, SetVmTicketVDSCommand(HostName = hosted_engine_1, HostId = e90e2ca0-e3b9-46d5-8fde-09fc1c5eed20, vmId=6ca4e6ae-a201-432b-b22a-2c6517fbd92c, ticket=pd2lTiu7w7Ra, validTime=7200,m userName=admin, userId=fdfc627c-d875-11e0-90f0-83df133b58cc), log id: 6257f73 2015-03-26 19:52:14,766 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp--127.0.0.1-8702-10) [7f6f1f09] FINISH, SetVmTicketVDSCommand, log id: 6257f73 2015-03-26 19:52:14,846 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp--127.0.0.1-8702-10) [7f6f1f09] Correlation ID: 7f6f1f09, Call Stack: null, Custom Event ID: -1, Message: user admin@internal initiated console session for VM krypto_f21
What am doing wrong? _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi, Could you confirm that using "reinstall" option in oVirt GUI when a host is in maintenance mode, is not destructive for the VMs of the DC ? BTW my 2 nodes stays in "unresponsive" state. Thanks Alain VONDRA Chargé d'exploitation des Systèmes d'Information Direction Administrative et Financière +33 1 44 39 77 76 UNICEF France 3 rue Duguay Trouin 75006 PARIS www.unicef.fr
On Mar 27, 2015, at 09:37 , VONDRA Alain <AVONDRA@unicef.fr> wrote:
Hi, Could you confirm that using "reinstall" option in oVirt GUI when a host is in maintenance mode, is not destructive for the VMs of the DC ?
It doesn't do anything to the shared storage, so you're safe:)
BTW my 2 nodes stays in "unresponsive" state.
well, reboot&reinstall may help…if not, one need to really start looking into why:) Thanks, michal
Thanks
Alain VONDRA Chargé d'exploitation des Systèmes d'Information Direction Administrative et Financière +33 1 44 39 77 76 UNICEF France 3 rue Duguay Trouin 75006 PARIS www.unicef.fr
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Thanks for your reply Michal, I've already done the reinstall, the hosts were up again. I'm in front of a new problem, but this one is closed Regards Alain VONDRA Chargé d'exploitation des Systèmes d'Information Direction Administrative et Financière +33 1 44 39 77 76 UNICEF France 3 rue Duguay Trouin 75006 PARIS www.unicef.fr -----Message d'origine----- De : Michal Skrivanek [mailto:michal.skrivanek@redhat.com] Envoyé : lundi 30 mars 2015 17:06 À : VONDRA Alain Cc : users@ovirt.org Objet : Re: [ovirt-users] Host reinstall option in oVirt On Mar 27, 2015, at 09:37 , VONDRA Alain <AVONDRA@unicef.fr> wrote:
Hi, Could you confirm that using "reinstall" option in oVirt GUI when a host is in maintenance mode, is not destructive for the VMs of the DC ?
It doesn't do anything to the shared storage, so you're safe:)
BTW my 2 nodes stays in "unresponsive" state.
well, reboot&reinstall may help…if not, one need to really start looking into why:) Thanks, michal
Thanks
Alain VONDRA Chargé d'exploitation des Systèmes d'Information Direction Administrative et Financière +33 1 44 39 77 76 UNICEF France 3 rue Duguay Trouin 75006 PARIS www.unicef.fr
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (4)
-
John Florian -
Michal Skrivanek -
Tomas Jelinek -
VONDRA Alain