still relevant?

(In reply to comment #1)
> still relevant?

iiuc spicec is deprecated.

yes, hence the request to change to use spice-gtk instead (although shouldn't this be virt-viewer?)

(In reply to Itamar Heim from comment #3)
> yes, hence the request to change to use spice-gtk instead (although
> shouldn't this be virt-viewer?)

good question, i'm all for using latest client.

michael - not fixed yet?

The solution to this bug should be similar to the example described in the following thread in the users list:

http://lists.ovirt.org/pipermail/users/2014-February/021638.html

Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.

code issue.

[root@jb-rhevm36 ~]# rpm -qa python rhevm-cli virt-viewer
virt-viewer-2.0-7.el6.x86_64
rhevm-cli-3.6.0.0-1.el6ev.noarch
python-2.6.6-64.el6.x86_64

~~~
[RHEVM shell (connected)]# console jb-test
  ================================================================================ UNKNOWN ERROR =============================================================================
                                                             spice viewer was not found, please install spice first.
  ============================================================================================================================================================================

[RHEVM shell (connected)]# console jb-test
  ================================================================================ UNKNOWN ERROR =============================================================================
                                             'ascii' codec can't encode character u'\xed' in position 10: ordinal not in range(128)
  ============================================================================================================================================================================
~~~

traceback when rhevm-shell run in debug:

~~~
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/cli/context.py", line 204, in execute_string
    self._execute_command(command)
  File "/usr/lib/python2.6/site-packages/cli/context.py", line 424, in _execute_command
    command.run(self)
  File "/usr/lib/python2.6/site-packages/cli/command/command.py", line 101, in run
    self.execute()
  File "/usr/lib/python2.6/site-packages/ovirtcli/command/console.py", line 99, in execute
    debug
  File "/usr/lib/python2.6/site-packages/ovirtcli/platform/posix/spice.py", line 80, in launch_spice_client
    title, ca_file, debug)
  File "/usr/lib/python2.6/site-packages/ovirtcli/platform/posix/spice.py", line 145, in launch_remote_viewer
    ca_text=ca_text.replace("\n", "\\n"),
UnicodeEncodeError: 'ascii' codec can't encode character u'\xed' in position 10: ordinal not in range(128)
~~~

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

please consider also improvement of:

    # No luck, no known command is available:
    raise Error, Messages.Error.NO_CONSOLE_FOUND % ('spice', 'spice')

we have two spice console viewers and the number could vary in the future. there's nothing like 'install spice'. imo it could be:

_a_ spice viewer was not found, please install _a_ spice _console viewer (eg. remote-viewer)_ first.

(would be doable to open console also in browser via spice-html? would be nice to have. eg. via `xdg-open default-web-browser $url'... you get the idea.)

The problem is probably the non ASCII characters in the subject of the certificate, as previously suggested. I wonder how that installation could be completed, as when I tried to reproduce it the setup application failed because of the same reason:

# engine-setup
...
[ ERROR ] Failed to execute stage 'Misc configuration': 'ascii' codec can't decode byte 0xc3 in position 38: ordinal not in range(128)

The main issue is caused by the non ASCII characters in the subject of the certificate of the host, and is addressed by the following patch:

  https://gerrit.ovirt.org/51404
  cli: Generate remote viewer config using UTF-8

The suggestion about the error messages is addressed by this other patch:

  cli: Improve the "no console found" messages
  https://gerrit.ovirt.org/51405

Opening using a browser is doable, but I guess it won't be easy. At the moment we are trying to avoid adding new functionality to the CLI. If you think it is important please open a separate RFE.

*** Bug 1303675 has been marked as a duplicate of this bug. ***

ok

works ok, if remote-viewer is not available, following msg informs the user.

[oVirt shell (connected)]# console jb-w7-x86
  ================================================================================ UNKNOWN ERROR =============================================================================
                                             a SPICE viewer was not found, please install a SPICE viewer (e.g. remote-viewer) first.
  ============================================================================================================================================================================