| Summary: | vdsmd can not start after upgrade from 0.9.4-23 to 0.9.8-0rc2 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Huang Wenlong <whuang> |
| Component: | vdsm | Assignee: | Dan Kenigsberg <danken> |
| Status: | CLOSED WONTFIX | QA Contact: | yeylon <yeylon> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.3 | CC: | abaron, acathrow, bazulay, berrange, cwei, dallan, iheim, mzhan, rwu, srevivo, ydu, ykaul |
| Target Milestone: | rc | Keywords: | Regression, Reopened, TestBlocker |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-06 10:35:05 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Huang Wenlong
2011-12-05 07:48:40 UTC
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 |