Created attachment 857169 [details]
console_options screen shot
Description of problem:
It is possible to choose for a VM with SPICE display type, in console_options, console invocation = SPICE HTML5 browser client (Tech preview).
This should not be allowed since the html5 client does not support the spice proxy.
When it is chosen, pressing the VM console icon, open a browser with the url:
Version-Release number of selected component (if applicable):
Why is it a problem?
We explicitly write there that it is in "Tech Preview".
Michal - do you see an issue with that?
it's indeed not compatible as spice_html5 depends on its own proxy in all cases. So if anything this should be documented as a separate setup of websocket proxy. We do support to deploy it on different host than engine effectively replacing the squid proxy for regular connections. It's about the same amount of manual effort for both proxies.
I'm not sure what docs say about this matter at the moment, there were a lot of changes in 3.3 but this is probably not there. Maybe kbase article suffices? (Marina, thoughts?)
If I understand the bug report properly, it says that:
1: open the console options dialog
2: select the "SPICE HTML5" console invocation
On the screen you will still see the "Enable SPICE Proxy" checkbox even the HTML5 does not support it.
It is indeed a bug, because it should be either disabled or not there at all.
BTW looking into the screen, none of the SPICE options there are supported by the HTML5 client.
AFAIK Franta is working on something which should solve this:
@Franta - comments?
@Tomas: Well, yes indeed. I've been working on another refactoring patch that takes differences in supported features into account.
Verified on rhevm 3.6.0-15
Moving 'requires_doc_text' to '-' and removing doc text. A note that SPICE proxy cannot be used with SPICE HTML5 was added to the 'SPICE Proxy' section of the Administration Guide as part of bug 1074917:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.