Bug 1007204
Summary: | qemu-img-rhev qemu-kvm-rhev-tools are not built for qemu-kvm-1.5.3-3.el7 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Xiaoqing Wei <xwei> |
Component: | qemu-kvm | Assignee: | Miroslav Rezanina <mrezanin> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 | CC: | acathrow, areis, hhuang, juzhang, lsu, michen, shuang, tpoitras, virt-maint, xuhan, xwei |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-1.5.3-40.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-06-13 10:10:05 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: | |||
Bug Depends On: | |||
Bug Blocks: | 895041, 1080820 |
Description
Xiaoqing Wei
2013-09-12 06:08:47 UTC
Additional info: qemu-kvm-rhev for rhel7.0 comes out but not completed. layout from brew about qemu-kvm-rhev x86_64 (build logs) qemu-kvm-common-rhev-1.5.3-3.el7.x86_64.rpm (info) (download) qemu-kvm-rhev-1.5.3-3.el7.x86_64.rpm (info) (download) qemu-kvm-rhev-debuginfo-1.5.3-3.el7.x86_64.rpm (info) (download) This behavior is on purpose. User should use rhel version of packages as there's no difference. So there's only core packages build for RHEL-7 based rhev. As qemu-kvm-rhev should be dependent on qemu-img package, please verify that this dependency is correctly enforced. If so, close this bz as NOTABUG. (In reply to Miroslav Rezanina from comment #2) > This behavior is on purpose. User should use rhel version of packages as > there's no difference. So there's only core packages build for RHEL-7 based > rhev. > > As qemu-kvm-rhev should be dependent on qemu-img package, please verify that > this dependency is correctly enforced. If so, close this bz as NOTABUG. Thanks for explanation first. Xwei is on PTO these days. I tested with latest qemu-kvm-rhev. Qemu-kvm-rhev in deed depends on qemu-img package. #rpm -q qemu-kvm-rhev-1.5.3-4.el7 --requires | grep qemu config(qemu-kvm-rhev) = 10:1.5.3-4.el7 ipxe-roms-qemu qemu-img = 10:1.5.3-4.el7 qemu-kvm-common-rhev = 10:1.5.3-4.el7 #rpm -ivh qemu-kvm-rhev-1.5.3-4.el7.x86_64.rpm error: Failed dependencies: qemu-img = 10:1.5.3-4.el7 is needed by qemu-kvm-rhev-10:1.5.3-4.el7.x86_64 (In reply to Miroslav Rezanina from comment #2) Hi Miroslav, > This behavior is on purpose. User should use rhel version of packages as > there's no difference. So there's only core packages build for RHEL-7 based > rhev. Just curious, why dont keep same way as rhel-6 based rhev, > > As qemu-kvm-rhev should be dependent on qemu-img package, please verify that > this dependency is correctly enforced. If so, close this bz as NOTABUG. yes, now it did dependent on qemu-img pkg, like C#3 Juzhang's steps. and this would make user a little bit inconvenient to install rhev pkgs, need to download both rhel and rhev rpms. Regards, Xiaoqing. *** Bug 1044300 has been marked as a duplicate of this bug. *** Fix included in qemu-kvm-1.5.3-40.el7 Checked latest rhel7 qemu-kvm-rhev build. 'qemu-img-rhev' and 'qemu-kvm-rhev-tools' has already built for qemu-kvm-rhev. x86_64 (build logs) libcacard-devel-rhev-1.5.3-43.el7.x86_64.rpm (info) (download) libcacard-rhev-1.5.3-43.el7.x86_64.rpm (info) (download) libcacard-tools-rhev-1.5.3-43.el7.x86_64.rpm (info) (download) qemu-img-rhev-1.5.3-43.el7.x86_64.rpm (info) (download) qemu-kvm-common-rhev-1.5.3-43.el7.x86_64.rpm (info) (download) qemu-kvm-rhev-1.5.3-43.el7.x86_64.rpm (info) (download) qemu-kvm-tools-rhev-1.5.3-43.el7.x86_64.rpm (info) (download) qemu-kvm-rhev-debuginfo-1.5.3-43.el7.x86_64.rpm (info) (download) This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request. |