Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
if port (tls-port) number is zero, treat it as no port number given.
This gives unnecessary network roundtrips to migration when only secure port is used on the destination.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
0. have a x509_DIR
1. run source qemu:
qemu-kvm -monitor stdio -spice tls-port=SPORT1,x509_dir=DIR,disable-ticketing
2. run destination qemu:
qemu-kvm -monitor stdio -spice tls-port=SPORT2,x509_dir=DIR,disable-ticketing
3. connect to the source qemu:
remote-viewer --spice-ca-file DIR/ca-cert.pem spice://my-laptop.example.com/?tls-port=SPORT1
4. instruct source qemu to migrate the client with zero port:
__com.redhat_spice_migrate_info my-laptop.example.com 0 SPORT2 "host subject"
Actual results:
spice-gtk tries to connect to port 0:
channel-main.c:1717 migrate_begin 25 my-laptop.example.com 0 SPORT2
channel-main.c:1578 migrate_channel_connect 1:0
spice-channel.c:126 main-1:0: spice_channel_constructed
spice-session.c:1628 new main channel, switching
spice-channel.c:2255 Open coroutine starting 0x2103460
spice-channel.c:2098 Started background coroutine 0x21034e8 for main-1:0
spice-channel.c:2122 connection failed, trying with TLS port
Expected results:
spice-gtk skips port and goes to TLS port right away
Additional info:
Comment 1Christophe Fergeau
2012-09-18 12:08:40 UTC
I don't think it attempts an non-SSL connection actually, the message comes from spice-channel.c:
reconnect:
c->sock = spice_session_channel_open_host(c->session, channel, c->tls);
if (c->sock == NULL) {
if (!c->tls) {
CHANNEL_DEBUG(channel, "connection failed, trying with TLS port");
c->tls = true; /* FIXME: does that really work with provided fd */
goto reconnect;
} else {
CHANNEL_DEBUG(channel, "Connect error");
emit_main_context(channel, SPICE_CHANNEL_EVENT, SPICE_CHANNEL_ERROR_CONNECT);
goto cleanup;
}
}
The actual connection is done in spice_session_channel_open_host from spice-session.c which starts with
if ((use_tls && !s->tls_port) || (!use_tls && !s->port))
return NULL;
c->tls and use_tls are FALSE or "connection failed, trying with TLS port" wouldn't appear, and s->port is null as well, so NULL is returned before any connection is attempted.
Comment 2Marc-Andre Lureau
2012-10-18 13:23:11 UTC
sent to ML
channel: improve debugging message
The open_host() can return FALSE when the connection is discarded or
skipped. Improve the message to not indicate a failure.
https://bugzilla.redhat.com/show_bug.cgi?id=858232
Comment 3Marc-Andre Lureau
2012-12-10 13:01:53 UTC
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.
http://rhn.redhat.com/errata/RHBA-2013-0343.html