Description of problem: [root@puma19 ~]# /etc/init.d/vdsmd start Please enter your authentication name: Please enter your password: Can't connect to default. Skipping. initctl: Job is already running: libvirtd vdsm: Running run_init_hooks vdsm: Running gencerts vdsm: Running reconfigure_sanlock vdsm: Running reconfigure_libvirt libvirt is already configured for vdsm vdsm: Running syslog_available vdsm: Running nwfilter vdsm: Running dummybr vdsm: Running load_needed_modules vdsm: Running tune_system vdsm: Running mkdirs vdsm: Running test_space vdsm: Running test_lo vdsm: Running test_conflicting_conf SUCCESS: ssl configured to true. No conflicts Starting up vdsm daemon: vdsm start [ OK ] Version-Release number of selected component (if applicable): IS15 How reproducible: 100% Steps to Reproduce: 1. Install IS15 2. Stop vdsm service 3. Try to start vdsm service Actual results: Starting vdsmd requires password. Expected results: Starting vdsmd will not require password
I saw that only once, and I think it was fixed as part of other fixes in the starting method. Can you please re-verify that in fresh install?
This is still happening to me on is15: [root@aqua-vds5 ~]# /etc/init.d/vdsmd restart Shutting down vdsm daemon: vdsm watchdog stop [ OK ] vdsm: Running run_final_hooks [ OK ] vdsm stop [ OK ] Please enter your authentication name: Please enter your password: Can't connect to default. Skipping. initctl: Job is already running: libvirtd vdsm: Running run_init_hooks vdsm: Running gencerts vdsm: Running reconfigure_sanlock vdsm: Running reconfigure_libvirt libvirt is already configured for vdsm vdsm: Running syslog_available vdsm: Running nwfilter libvir: Network Filter Driver error : Requested operation is not valid: nwfilter is in use vdsm: Running dummybr vdsm: Running load_needed_modules vdsm: Running tune_system vdsm: Running mkdirs vdsm: Running test_space vdsm: Running test_lo vdsm: Running test_conflicting_conf SUCCESS: ssl configured to true. No conflicts Starting up vdsm daemon: vdsm start [ OK ] [root@aqua-vds5 ~]# rpm -q vdsm vdsm-4.12.0-138.gitab256be.el6ev.x86_64
Found the issue. stopping libvirt-quests service when sasl is configured raises this message that stop the starting process until intervention. Checking for solution.
*** This bug has been marked as a duplicate of bug 1010693 ***
*** Bug 1010693 has been marked as a duplicate of this bug. ***
Verified: [root@master-vds13 ~]# /etc/init.d/vdsmd restart Shutting down vdsm daemon: vdsm watchdog stop [ OK ] vdsm: Running run_final_hooks [ OK ] vdsm stop [ OK ] initctl: Job is already running: libvirtd vdsm: Running run_init_hooks vdsm: Running gencerts vdsm: Running reconfigure_sanlock vdsm: Running reconfigure_libvirt libvirt is already configured for vdsm vdsm: Running syslog_available vdsm: Running nwfilter vdsm: Running dummybr vdsm: Running load_needed_modules vdsm: Running tune_system vdsm: Running mkdirs vdsm: Running test_space vdsm: Running test_lo vdsm: Running test_conflicting_conf SUCCESS: ssl configured to true. No conflicts Starting up vdsm daemon: vdsm start [ OK ] [root@master-vds13 ~]# rpm -q vdsm vdsm-4.12.0-170.el6ev.x86_64
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.
Cheryn, I am sorry about our slow response, but this bug is a regression introduced during the rhev-3.3 development cycle. The bug was not visible to any user, and as such, it should not be documented.
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