Bug 1362192
Summary: | Use el7_2 instead of el7 suffix for the rpm | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Fabian Deutsch <fdeutsch> |
Component: | rhev-hypervisor-ng | Assignee: | Ryan Barry <rbarry> |
Status: | CLOSED ERRATA | QA Contact: | cshao <cshao> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.0.0 | CC: | dfediuck, dguo, fdeutsch, gklein, huzhao, leiwang, weiwang, yaniwang, ycui |
Target Milestone: | ovirt-4.0.2 | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-08-23 21:08:18 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Fabian Deutsch
2016-08-01 13:33:12 UTC
Test version: redhat-virtualization-host-4.0-20160803.3 imgbased-0.7.4-0.1.el7ev.noarch Test steps: 1. Nount RHVH.iso 2. Check the rpm Test result: redhat-virtualization-host-image-update-4.0-20160803.3.el7_2.noarch.rpm So the bug is fixed, change bug status to VERIFIED. Hi Fabian, Do we need use el7_2 instead of el7 suffix for the below rpm? # rpm -qa | grep redhat-release-virtualization-host-4.0-0.26.el7.x86_64 redhat-release-virtualization-host-4.0-0.26.el7.x86_64 # rpm -qa | grep imgbased-0.7.4-0.1.el7ev.noarch imgbased-0.7.4-0.1.el7ev.noarch # rpm -qa | grep redhat-virtualization-host-image-update-placeholder-4.0-0.26.el7.noarch redhat-virtualization-host-image-update-placeholder-4.0-0.26.el7.noarch No, inside the image it is not relevant what suffix is used. It must only be used for the outer rpm Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-1702.html |