Created attachment 805192 [details] engine.log, vdsm.log from hosts, libvirtd.log from hosts Description of problem: Migration fails... 2013-Sep-30, 14:33 Migration failed due to Error: Fatal error during migration (VM: test-jb-rh6-x86, Source: dell-r210ii-03, Destination: dell-r210ii-13). --%-- Thread-5700::ERROR::2013-09-30 14:33:31,552::vm::238::vm.Vm::(_recover) vmId=`36158391-dfb4-4d96-bc13-b4419adcd9a8`::unsupported configuration: Unable to find security driver for label selinux Thread-5700::ERROR::2013-09-30 14:33:31,618::vm::318::vm.Vm::(run) vmId=`36158391-dfb4-4d96-bc13-b4419adcd9a8`::Failed to migrate Traceback (most recent call last): File "/usr/share/vdsm/vm.py", line 305, in run self._startUnderlyingMigration() File "/usr/share/vdsm/vm.py", line 382, in _startUnderlyingMigration None, maxBandwidth) File "/usr/share/vdsm/vm.py", line 827, in f ret = attr(*args, **kwargs) File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line 76, in wrapper ret = f(*args, **kwargs) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1178, in migrateToURI2 if ret == -1: raise libvirtError ('virDomainMigrateToURI2() failed', dom=self) libvirtError: unsupported configuration: Unable to find security driver for label selinux --%-- --%-- 2013-09-30 12:33:31.523+0000: 2579: error : virNetClientProgramDispatchError:174 : unsupported configuration: Unable to find security driver for label selinux --%-- Version-Release number of selected component (if applicable): is16 source host: libvirt-0.10.2-27.el6.x86_64, dsm-4.12.0-156.git6e499d6.el6ev.x86_64, selinux-policy-3.7.19-216.el6.noarch, qemu-kvm-rhev-0.12.1.2-2.406.el6.x86_64 dest host: libvirt-0.10.2-27.el6.x86_64, vdsm-4.12.0-156.git6e499d6.el6ev.x86_64, selinux-policy-3.7.19-216.el6.noarch, qemu-kvm-rhev-0.12.1.2-2.407.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
flagging storge to check if related to late storage changes
This is not the storage related problem and looks like a virt issue. According to Federico, possibly the problem is that selinux is on but libvirt does not load the selinux driver since it is disabled in the conf file. Please attach /etc/libvirt/qemu.conf to verify. If this is correct then this is due to a libvirt version that accidentally was released with this off by default and the solution would be to bump the conf version so that vdsm would reconfigure it upon startup (workaround is just to change this config and reload).
# hostname ; egrep -v "^#|^[ \t]*$" /etc/libvirt/qemu.conf dell-r210ii-03.rhev.lab.eng.brq.redhat.com dynamic_ownership=0 spice_tls=1 save_image_format="lzop" spice_tls_x509_cert_dir="/etc/pki/vdsm/libvirt-spice" lock_manager="sanlock" # grep selinux /etc/libvirt/qemu.conf # security_driver = [ "selinux", "apparmor" ] #security_driver = "selinux" # hostname ; egrep -v "^#|^[ \t]*$" /etc/libvirt/qemu.conf dell-r210-13.rhev.lab.eng.brq.redhat.com dynamic_ownership=0 security_driver="none" spice_tls=1 save_image_format="lzop" spice_tls_x509_cert_dir="/etc/pki/vdsm/libvirt-spice" lock_manager="sanlock" auto_dump_path="/var/log/core" # grep selinux /etc/libvirt/qemu.conf # security_driver = [ "selinux", "apparmor" ] #security_driver = "selinux"
IIUC this is a setup issue addressed by http://gerrit.ovirt.org/#/c/19005/. Further details and debug logs can be found in bug 1006952
Interesting. Then why it is working in one direction and other one not? As I have same versions of components... Is there a workaround?
Verified in vdsm-4.13.0-0.2.beta1.el6ev.x86_64 (is18). VM migration finishes successfully, no errors in vdsm logs nor engine log.
Hello Team, One of our cus facing same issue . After upgrading vdsm on one (destination host) of the host this error is noticed . source vdsm-4.10.2-27.0.el6ev.x86_64 Mon Nov 25 10:44:46 2013 qemu-kvm-rhev-0.12.1.2-2.415.el6.x86_64 Mon Nov 25 10:44:45 2013 libvirt-0.10.2-29.el6.1.x86_64 Mon Nov 25 10:44:07 2013 source vdsm-4.10.2-25.1.el6ev.x86_64 Tue 01 Oct 2013 06:05:32 PM CEST qemu-kvm-rhev-0.12.1.2-2.355.el6_4.7.x86_64 Tue 01 Oct 2013 06:04:57 PM CEST libvirt-0.10.2-18.el6_4.14.x86_64 Tue 01 Oct 2013 06:05:30 PM CEST Do we have any workaround for this ? Can i ask customer to downgrade the vdsm package to vdsm-4.10.2-25.1 ? Regards, Jaison R
is the selinux version matching the one in bug 1006952 ?
This bug is currently attached to errata RHBA-2013:15291. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
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-2014-0040.html