Bug 827897
Summary: | Upgrade of libvirt breaks VDSM (due to broken link in /etc/init/libvirtd.conf) | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Yaniv Kaul <ykaul> |
Component: | vdsm | Assignee: | Douglas Schilling Landgraf <dougsland> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Haim <hateya> |
Severity: | high | Docs Contact: | |
Priority: | urgent | ||
Version: | 6.3 | CC: | abaron, acathrow, bazulay, byount, dallan, dyasny, dyuan, iheim, jdenemar, jkt, mzhan, rhodain, rwu, whuang, yeylon, ykaul |
Target Milestone: | rc | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | infra | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-03-01 04:58:12 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Yaniv Kaul
2012-06-03 14:36:35 UTC
Hi , Yaniv I know this issue , the cause is your host installed a old version vdsm , /etc/init/libvirtd.conf -> /usr/share/doc/libvirt-0.9.4/libvirtd.upstart this soft link it created by old vdsm setup scripts , but new vdsm use "copy" instead of "link" ,so in my host I can not reproduce this bug . the bad file is not created by libvirt, so I think it is not a libvirt's bug version in my host libvirt-0.9.4-23.el6_2.8.x86_64 vdsm-4.9-112.8.el6_2.x86_64 qemu-kvm-0.12.1.2-2.295.el6.x86_64 # ll /etc/init/libvirtd.conf (it is a real file not a link ) -rw-r--r--. 1 root root 991 May 31 22:43 /etc/init/libvirtd.conf Wenlong I agree that this is not a libvirt bug. The /etc/init/libvirtd.conf link is not created by libvirt. IIRC someone (danpb?) somewhere mentioned that a package (which would be vdsm in this case) can install a script which is executed when another package is upgraded... such script could be used to update the link. However, I don't remember the details and my memory can even be completely wrong... I'm not at all sure whose BZ this is, but it's most certainly a bug, so I'm reopening. My initial impression is that VDSM needs to be updated to know about the new libvirt version, so I'm changing the component to VDSM. yaniv - if this is still relevant, shouldn't this be a 6.3 blocker for vdsm (even though one can upgrade libvirt without upgrading vdsm)? raising priority until this is analyzed according to danken: "the softlink was only created in beta cycle of 3.0. no customer should have it (we used copy by GA). a maybe on a release note in case some customers have upgraded from beta." moving to ON_QA to check this and close if not reproduced on clean vdsm. (In reply to comment #7) > according to danken: > "the softlink was only created in beta cycle of 3.0. no customer should have > it (we used copy by GA). > a maybe on a release note in case some customers have upgraded from beta." > > moving to ON_QA to check this and close if not reproduced on clean vdsm. Just verified the above by installing clean vdsm build from version vdsm-4.9-112.14, checked /etc/init/ and there was no link to libvirt upstart, then, added rhel6.3 repo, upgraded to vdsm-4.9-113.1.el6.x86_64, then upgraded libvirt, and everything went smooth. we shall add a RN. *** Bug 841042 has been marked as a duplicate of this bug. *** moving to verified as per comment 8. |