Description of problem: libvirt-reconfigure performs libvirtd service restart, if supervdsmd was started before running the reconfigure, we should restart supervdsmd after libvirtd restart to re-established the connection between the two. ovirt-host-deploy takes care of restarting vdsmd after reconfigure. Before vdsm 3.3 that contains the separation of supervdsmd to external service, restart vdsmd was enough - as it was restarting also supervdsm process. Now, when supervdsmd is external to vsdmd we should take care of it separately, and for backwards compatibility it's not enough to add it only for new version of ovirt-host-deploy. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. run vdsm-tool reconfigure-libvirt force 2. call vdsClient setupNetworks .. Actual results: supervdsmd fails to execute the setupNetworks verb that contain calls to libvirt, get an sigterm and restarts. first call fails, second works. Expected results: supervdsmd should response normally after reconfigure libvirt and perform the action.
verified on vdsm-4.13.0-0.2.beta1.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.
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