Hide Forgot
Description of problem: SSIA. Might be symptom of some hidden problem. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. run VM via rhevm, set a ticket manually to it 2. connect to machine using -w, --ca-file and --host-subject options 3. Actual results: connection fails several times and it must be repeated to succeed eventually Expected results: connection is successfull right away Additional info: CLI output is in attachment
Created attachment 514048 [details] CLI output
Does this work if you use the UserPortal?
spicec fired by UP works fine, so I've set up initial priorities and severities to 'low'.
Since RHEL 6.2 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
moved to 6.3 according to comment 4 and it does impact user experience according to comment3
Additional info from yesterday debugging with Uri & teuf: 1. it is most reproducible with --secure-channels and -p ommited: spicec --ca-file <file> --host-subject <subject> -w <pw> -h <host> -s <sport> With command line above, the bug is ~50 % reproducible and you don't have to wait. Just keep reconnecting and on 3rd-5th attempt, the bug should occur 2. qemu-kvm is launched by rhev-m 3. qemu-kvm log of 2 unsuccessful attempts and one succesfull looks like this: reds_accept_ssl_connection: __reds_accept_connection: reds_accept_ssl_connection: SSL_ERROR_WANT_READ reds_accept_ssl_connection: __reds_accept_connection: reds_accept_ssl_connection: SSL_ERROR_WANT_READ reds_handle_ssl_accept: reds_handle_ssl_accept: reds_handle_ssl_accept: SSL_accept failed, error=5 reds_accept_ssl_connection: __reds_accept_connection: reds_accept_ssl_connection: SSL_ERROR_WANT_READ reds_accept_ssl_connection: __reds_accept_connection: reds_accept_ssl_connection: SSL_ERROR_WANT_READ reds_disconnect: red_dispatcher_shutdown_cursor_peer: red_dispatcher_shutdown_peer: handle_dev_input: cursor disconnect handle_dev_input: disconnect reds_handle_ssl_accept: reds_handle_ssl_accept: SSL_accept failed, error=5 reds_handle_ssl_accept: reds_handle_ssl_accept: SSL_accept failed, error=5 reds_handle_ssl_accept: reds_handle_ssl_accept: SSL_accept failed, error=5 reds_accept_ssl_connection: __reds_accept_connection: reds_accept_ssl_connection: SSL_accept failed, error=5, errno=Success reds_accept_ssl_connection: __reds_accept_connection: reds_accept_ssl_connection: SSL_ERROR_WANT_READ reds_handle_ssl_accept: reds_handle_ssl_accept: reds_handle_new_link: reds_handle_read_header_done: reds_handle_read_link_done: reds_handle_read_link_done: Peer doesn't support AUTH selection reds_handle_ticket: reds_handle_link: reds_handle_main_link: reds_show_new_channel: channel 1:0, connected successfully, over Secure link reds_main_handle_message: agent start reds_accept_ssl_connection: __reds_accept_connection: reds_accept_ssl_connection: SSL_ERROR_WANT_READ reds_main_handle_message: net test: latency 0.890000 ms, bitrate 167074563 bps (159.334720 Mbps) reds_accept_ssl_connection: __reds_accept_connection: reds_accept_ssl_connection: SSL_ERROR_WANT_READ reds_handle_ssl_accept: reds_handle_ssl_accept: reds_accept_ssl_connection: __reds_accept_connection: reds_accept_ssl_connection: SSL_ERROR_WANT_READ reds_accept_ssl_connection: __reds_accept_connection: reds_accept_ssl_connection: SSL_ERROR_WANT_READ reds_accept_ssl_connection: __reds_accept_connection: reds_accept_ssl_connection: SSL_ERROR_WANT_READ reds_handle_ssl_accept: reds_handle_new_link: reds_handle_ssl_accept: reds_handle_new_link: reds_handle_ssl_accept: reds_handle_new_link: reds_handle_ssl_accept: reds_handle_new_link: reds_handle_ssl_accept: reds_handle_new_link: reds_handle_read_header_done: reds_handle_read_link_done: reds_handle_read_link_done: Peer doesn't support AUTH selection reds_handle_read_header_done: reds_handle_read_link_done: reds_handle_read_link_done: Peer doesn't support AUTH selection reds_handle_read_header_done: reds_handle_read_link_done: reds_handle_read_link_done: Peer doesn't support AUTH selection reds_handle_read_header_done: reds_handle_read_link_done: reds_handle_read_link_done: Peer doesn't support AUTH selection reds_handle_read_header_done: reds_handle_read_link_done: reds_handle_read_link_done: Peer doesn't support AUTH selection reds_handle_ticket: reds_handle_link: reds_show_new_channel: channel 5:0, connected successfully, over Secure link reds_handle_ticket: reds_handle_link: reds_show_new_channel: channel 3:0, connected successfully, over Secure link inputs_link: reds_handle_ticket: reds_handle_link: reds_show_new_channel: channel 4:0, connected successfully, over Secure link red_dispatcher_set_cursor_peer: handle_dev_input: cursor connect reds_handle_ticket: reds_handle_link: reds_show_new_channel: channel 2:0, connected successfully, over Secure link red_dispatcher_set_peer: handle_dev_input: connect reds_handle_ticket: handle_new_display_channel: jpeg disabled handle_new_display_channel: zlib-over-glz disabled reds_handle_link: reds_show_new_channel: channel 6:0, connected successfully, over Secure link
concentrating on virt-viewer in 6.3
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Closing as WONTFIX, spice-client was replaced by virt-viewer which is now supported client. This bug was not reproducible with virt-viewer, If you can reproduce with remote-viewer, please file a bug for virt-viewer. Thanks.