Description of problem: The VDSM version in RHS build 20130515.n.0 does not allow server to be added via RHSC bb1 Work around: - Remove vdsm rpms. - Install VDSM from rhsc/bb1 repo. Version-Release number of selected component (if applicable): RHSC: bb1 RHS: http://rhsqe-repo.lab.eng.blr.redhat.com/iso/rhs2.1/RHS-2.1-20130515.n.0-RHS-x86_64-DVD1.iso How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Matt, can you provide the version of vdsm after reinstalling or the repo that you have configured?
Created a new 20130515.n.0 VM, and the did the following: rpm -qa | grep vdsm vdsm-python-4.10.2-18.0.1.el6rhs.x86_64 vdsm-gluster-4.10.2-18.0.1.el6rhs.noarch vdsm-xmlrpc-4.10.2-18.0.1.el6rhs.noarch vdsm-cli-4.10.2-18.0.1.el6rhs.noarch vdsm-4.10.2-18.0.1.el6rhs.x86_64 vdsm-reg-4.10.2-18.0.1.el6rhs.noarch service vdsmd status VDS daemon is not running service vdsmd start vdsm: libvirt already configured for vdsm [ OK ] Starting iscsid: vdsm: Failed to define network filters on libvirt [FAILED]
Hope the system received the following error messages in /var/log/libvirt.log ... 2013-05-30 08:50:26.935+0000: 1839: error : virNetSASLSessionServerStep:614 : authentication failed: Failed to start SASL negotiation: -20 (SASL(-13): user not found: no secret in database) 2013-05-30 08:50:26.935+0000: 1839: error : remoteDispatchAuthSaslStep:2750 : authentication failed: authentication failed ... By observing the above log messages; it's clear that its failed with an authentication error. Quick fix: ~~~~~~~~~~ Just run the following commands: 1) vdsm-tool set-saslpasswd 2) service vdsmd restart
Which version of vdsm was removed? This bug could be a dup of bug 902346.
Dan, the error appears on installing vdsm from RHS 2.1 ISO. And was fixed as per comment 5.
Failed to verify. This fix apparently did not make it into the last RHS ISO. RHSC: bb4 RHS: RHS-2.1-20130628.n.0-RHS-x86_64-DVD1.iso After running the quick-fix commands mentioned in comment-5, the server added with no failures. Please reset to on_qa once the RHS iso has the proper fix.
Following are the specific errors seen in host-deploy logs: ------ 2013-07-08 07:36:09 DEBUG otopi.plugins.otopi.services.rhel plugin.execute:412 execute-output: ('/sbin/service', 'vdsmd', 'start') stdout: vdsm: libvirt already configured for vdsm [ OK ] Starting iscsid: vdsm: Failed to define network filters on libvirt[FAILED] 2013-07-08 07:36:09 DEBUG otopi.plugins.otopi.services.rhel plugin.execute:417 execute-output: ('/sbin/service', 'vdsmd', 'start') stderr: 2013-07-08 07:36:09 DEBUG otopi.context context._executeMethod:130 method exception Traceback (most recent call last): File "/tmp/ovirt-Ex1iY6m70O/pythonlib/otopi/context.py", line 120, in _executeMethod method['method']() File "/tmp/ovirt-Ex1iY6m70O/otopi-plugins/ovirt-host-deploy/vdsm/packages.py", line 153, in _start self.services.state('vdsmd', True) File "/tmp/ovirt-Ex1iY6m70O/otopi-plugins/otopi/services/rhel.py", line 184, in state 'start' if state else 'stop' File "/tmp/ovirt-Ex1iY6m70O/otopi-plugins/otopi/services/rhel.py", line 96, in _executeServiceCommand raiseOnError=raiseOnError File "/tmp/ovirt-Ex1iY6m70O/pythonlib/otopi/plugin.py", line 422, in execute command=args[0], RuntimeError: Command '/sbin/service' failed to execute 2013-07-08 07:36:09 ERROR otopi.context context._executeMethod:139 Failed to execute stage 'Closing up': Command '/sbin/service' failed to execute -------
'vdsm-tool set-saslpasswd' command in post of vdsm.rpm fails during installation time of RHS. This is because the installer runs in selinux enabled mode whereas RHS has no selinux policy (note: RHS runs with selinux disabled). vdsm-tool crashes on 'import seobject' ie it fails on every call. Acceptable solution is avoid using vdsm-tool in spec file scriptlets and run appropriate command till RHS supports selinux
Workaround is to run RHS installation with 'selinux=0' in ISO boot.
Patch is under review https://code.engineering.redhat.com/gerrit/9944
*** Bug 980056 has been marked as a duplicate of this bug. ***
Verified fixed bb6 & RHS-2.1-20130717.
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-1262.html