Hide Forgot
Description of problem: libvirt update from 0.9.4-23 to 0.9.8-0rc2 the vdsmd can not start successfully /etc/init/libvirtd.conf -> /usr/share/doc/libvirt-0.9.4/libvirtd.upstart this link lost , it do not be updated after upgrade . Version-Release number of selected component (if applicable): libvirt-0.9.8-0rc2.el6.x86_64 vdsm-4.9-111.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. update libvirt from 0.9.4-23 to 0.9.8-0rc2 rpm -Uvh * 2.clean the vdsm's config from libvirtd.conf qemu.conf libvirtd files 3.restart vdsmd # /etc/init.d/vdsmd restart Shutting down vdsm daemon: vdsm watchdog stop [ OK ] vdsm stop [ OK ] Stopping libvirtd daemon: libvirtd: libvirtd is managed by upstart and started, use initctl instead vdsm: libvirt already configured for vdsm [ OK ] Starting iscsid: diff: /etc/init/libvirtd.conf: No such file or directory /bin/cp: not writing through dangling symlink `/etc/init/libvirtd.conf' vdsm: one of the dependent services did not start, error co[FAILED] Actual results: vdsmd can not start Expected results: vdsmd can start Additional info: If fixed the soft link then the vdsmd can start successfully .
We can't know the universe of links that point to libvirt's installed files. This is not a bug.
(In reply to comment #3) > We can't know the universe of links that point to libvirt's installed files. > This is not a bug. Hi,Dave This link is created by vdsmd ... packaged=`/bin/rpm -ql libvirt | /bin/grep libvirtd.upstart | \ /usr/bin/tail -1` target=/etc/init/libvirtd.conf if ! diff -q "$packaged" "$target" >/dev/null; then /bin/cp -p "$packaged" "$target" || return 1 /sbin/initctl reload-configuration fi ... maybe I need clone this bug to vdsm ,thanks Wenlong
Hi,danken the lost soft link is created by /etc/init.d/vdsmd , the scripts need fix it so I think maybe I need re-assign this bug to you(vdsm) , ok ? Wenlong
If there are problems with the symlink becoming broken upon uprade of libvirt, then the VDSM rpm spec can use a '%trigger' script to run logic to deal with upgrades.
Wenlong, which link are you referring to? vdsm-4.9-110 used to create a soft link from /etc/init/libvirtd.conf, but that has changed due to bug 733000 (now we have a copy). The released vdsm-4.9-112.1 does not create such a link. Unfortunately, we do not plan to support an upgrade path from rhev-3.0-beta-2's vdsm to rhev-3.0-ga's. You would have to remove vdsm, make sure the link is gone, and re-install. Please re-open the bug if it somehow reproduces with vdsm-4.9-112.1.
(In reply to comment #7) > Wenlong, which link are you referring to? vdsm-4.9-110 used to create a soft > link from /etc/init/libvirtd.conf, but that has changed due to bug 733000 (now > we have a copy). The released vdsm-4.9-112.1 does not create such a link. > > Unfortunately, we do not plan to support an upgrade path from rhev-3.0-beta-2's > vdsm to rhev-3.0-ga's. You would have to remove vdsm, make sure the link is > gone, and re-install. > > Please re-open the bug if it somehow reproduces with vdsm-4.9-112. Thanks for your reply , I will remove the old vdsm then reinstall vdsm-4.9-112.1 . Wenlong
(In reply to comment #7) > Wenlong, which link are you referring to? vdsm-4.9-110 used to create a soft > link from /etc/init/libvirtd.conf, but that has changed due to bug 733000 (now > we have a copy). The released vdsm-4.9-112.1 does not create such a link. > > Unfortunately, we do not plan to support an upgrade path from rhev-3.0-beta-2's > vdsm to rhev-3.0-ga's. You would have to remove vdsm, make sure the link is > gone, and re-install. > > Please re-open the bug if it somehow reproduces with vdsm-4.9-112.1. Hi, Dan I installed the vdsm-4.9-122.1 ,it cp the /etc/init/libvirtd.conf from /usr/share/doc/libvirt-0.9.8/libvirtd.upstart ,everything is OK ,thank you very much . Wenlong