Bug 1429485
Summary: | [RFE] Imgbased layers should be named with '%{name}-%{version}-%{release}' instead of %{name}-%{version} | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Pavol Brilla <pbrilla> |
Component: | ovirt-node-ng | Assignee: | Yuval Turgeman <yturgema> |
Status: | CLOSED ERRATA | QA Contact: | cshao <cshao> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0.7 | CC: | bgraveno, cshao, dfediuck, mgoldboi, rbarry, ycui, yturgema |
Target Milestone: | ovirt-4.2.0 | Keywords: | FutureFeature, Reopened |
Target Release: | --- | Flags: | rbarry:
needinfo-
yturgema: needinfo- |
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: |
undefined
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-15 17:57:40 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
Pavol Brilla
2017-03-06 13:18:36 UTC
imgbase w displays the name of the lvm layer, not the version of the rpm so this is ok. For the version of imgbase, you can use imgbase --version (which is not the same as the rpm version as well btw). Hey -- re-opening this. I'll change the description. This bug isn't about "imgbase w", but a tracker for layers to actually follow this naming to make versioning easily identifiable, unless I've misunderstood Pavol. Shouldn't we set this as RFE ? This should definitely be an RFE. Test version: redhat-virtualization-host-4.2-20180420.0 Imgbased layers show as following: # imgbase w You are on rhvh-4.2.2.1-0.20180420.0+1 So the bug is fixed, change bug status to VERIFIED. 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://access.redhat.com/errata/RHSA-2018:1524 BZ<2>Jira Resync |