Description of problem: Suggesting that both the Admin and Installation Guides state that the vdsmd service should be restarted if the libvirt packages are updated. Currently the Admin Guide (19.1.5 Updating Red Hat Enterprise Linux Virtualization Hosts) and the Installation Guide (5.1.5 Updating Red Hat Enterprise Linux Virtualization Hosts) state that "If a package such as VDSM or libvirt was updated, you must restart that service to get the new functionality". Perhaps an additional sentence could be added or the current one modified to state that vdsm should be restarted if libvirt is upgraded. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Fixed in 10732.
Documentation Link ------------------------------ http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.3/html-single/Administration_Guide/index.html#Updating_Red_Hat_Enterprise_Linux_Virtualization_Hosts What Changed ------------------------------ The following topic was revised to add the line "Moreover, if the libvirt package is updated, you must restart the VDSM service." Updating Red Hat Enterprise Linux Virtualization Hosts [ 10732-588947 ] Updated revision history: [ 21114-589050 ] NVR ------------------------------ Red_Hat_Enterprise_Virtualization-Administration_Guide-3.3-en-US-3.3-47 Moving to ON_QA.
Hi Andrew, Does this only apply to the 3.3 release? Cannot see the text in 3.4. Cheers, Julie