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:
libvirt on DST Host, doesn't listen on its designated port (16514)
its listens to 16509
Version-Release number of selected component (if applicable):
How reproducible:
Not Always
Steps to Reproduce:
1.Migrate a VM from SRC Host to a DST Host
2.If the DST Host doesnt listen on the same port of libvirt as SRC host it will fail (TCP 16514)
3.
Actual results:
VM fails to migrate
Expected results:
VM Should migrate successfully
Additional info:
Libvirt Log
-----------------------------------
12:04:10.846: 9821: error : remoteIO:10569 : operation failed: Failed to connect to remote libvirt URI qemu+tls://10.16.33.116/syst
em
VDSM - fails migration
-----------------------------------
Thread-114::ERROR::2011-05-19 12:04:14,833::vm::456::vm.Vm::(run) vmId=`edc5a15c-1041-4a0a-9421-3cbd2ed8ec34`::Traceback (most rece
nt call last):
File "/usr/share/vdsm/vm.py", line 447, in run
self._startUnderlyingMigration()
File "/usr/share/vdsm/libvirtvm.py", line 281, in _startUnderlyingMigration
libvirt.VIR_MIGRATE_PEER2PEER, None, maxBandwidth)
File "/usr/share/vdsm/libvirtvm.py", line 306, in f
ret = attr(*args, **kwargs)
File "/usr/share/vdsm/libvirtconnection.py", line 59, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 576, in migrateToURI
if ret == -1: raise libvirtError ('virDomainMigrateToURI() failed', dom=self)
libvirtError: operation failed: Failed to connect to remote libvirt URI qemu+tls://10.16.33.116/system
===============================================
===============================================
10.16.33.113 (SRC Host)
tcp 0 0 0.0.0.0:16514 0.0.0.0:* LISTEN 0 18587 2627/libvirtd
--------------------
10.16.33.116 (DST Host)
tcp 0 0 0.0.0.0:16509 0.0.0.0:* LISTEN 0 18085 2547/libvirtd
I need much more information on what was going on with your dst host in the past. Did you change ssl from true to false manually? could you attach /etc/libvirt/{qemu,libvirtd}.conf ?
I suspect this is a dup of 684764, but I'm not yet sure.
qemu.conf has
listen_tcp=1 # by vdsm
listen_tls=0 # by vdsm
so it is clear that it was previously installed with ssl=false. It is unfortunate that future installations with ssl=true do not fix those configurations, and that is what bug 684764 is about.
*** This bug has been marked as a duplicate of bug 684764 ***
Description of problem: libvirt on DST Host, doesn't listen on its designated port (16514) its listens to 16509 Version-Release number of selected component (if applicable): How reproducible: Not Always Steps to Reproduce: 1.Migrate a VM from SRC Host to a DST Host 2.If the DST Host doesnt listen on the same port of libvirt as SRC host it will fail (TCP 16514) 3. Actual results: VM fails to migrate Expected results: VM Should migrate successfully Additional info: Libvirt Log ----------------------------------- 12:04:10.846: 9821: error : remoteIO:10569 : operation failed: Failed to connect to remote libvirt URI qemu+tls://10.16.33.116/syst em VDSM - fails migration ----------------------------------- Thread-114::ERROR::2011-05-19 12:04:14,833::vm::456::vm.Vm::(run) vmId=`edc5a15c-1041-4a0a-9421-3cbd2ed8ec34`::Traceback (most rece nt call last): File "/usr/share/vdsm/vm.py", line 447, in run self._startUnderlyingMigration() File "/usr/share/vdsm/libvirtvm.py", line 281, in _startUnderlyingMigration libvirt.VIR_MIGRATE_PEER2PEER, None, maxBandwidth) File "/usr/share/vdsm/libvirtvm.py", line 306, in f ret = attr(*args, **kwargs) File "/usr/share/vdsm/libvirtconnection.py", line 59, in wrapper ret = f(*args, **kwargs) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 576, in migrateToURI if ret == -1: raise libvirtError ('virDomainMigrateToURI() failed', dom=self) libvirtError: operation failed: Failed to connect to remote libvirt URI qemu+tls://10.16.33.116/system =============================================== =============================================== 10.16.33.113 (SRC Host) tcp 0 0 0.0.0.0:16514 0.0.0.0:* LISTEN 0 18587 2627/libvirtd -------------------- 10.16.33.116 (DST Host) tcp 0 0 0.0.0.0:16509 0.0.0.0:* LISTEN 0 18085 2547/libvirtd