RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 853092 - rhev-h: supported vdsm compatibility versions should be supplied along with rhev-h ISOs
Summary: rhev-h: supported vdsm compatibility versions should be supplied along with r...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rhev-hypervisor6
Version: 6.3
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Mike Burns
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 842767 856827
TreeView+ depends on / blocked
 
Reported: 2012-08-30 13:39 UTC by Einav Cohen
Modified: 2016-04-26 14:16 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: Add a file with RHEV-M compatibility information to the RHEV-H rpm. Reason: This is an internal enhancement to make upgrade from a RHEV-M server better. Result (if any): When installing the rhev-hypervisor6 rpm, a new file called vdsm-compatibility-<version>.txt will appear in /usr/share/rhev-hypervisor. This will contain information used by RHEV-M to determine if the image is a valid upgrade for a managed host.
Clone Of:
Environment:
Last Closed: 2013-02-28 18:58:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0579 0 normal SHIPPED_LIVE Important: rhev-hypervisor6 security, bug fix, and enhancement update 2013-02-28 23:55:03 UTC

Description Einav Cohen 2012-08-30 13:39:12 UTC
Description of problem:
[See Bug 842767]
in order to display in RHEV-M GUI only available RHEV-H ISOs for upgrade that are relevant to the selected RHEV-H Host, each ISO need to report (either via the version.txt file or a separate file) its supported vdsm compatibility versions.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Mike Burns 2012-09-10 13:00:34 UTC
What format and information is needed?  I don't particularly like hard coding information like this, but it should be doable.

Comment 3 Einav Cohen 2012-09-10 13:57:16 UTC
(In reply to comment #2)
> What format and information is needed?  I don't particularly like hard
> coding information like this, but it should be doable.

passing the question on to Bug 842767 assignee, Shahar.
[Shahar: This needs to be confirmed with Barak/Itamar, but I think we need information similar to the "clusterLevels" data being returned as part of the "getVdsCaps()" vdsm response (e.g. "['3.0', '3.1']")]

Comment 4 Shahar Havivi 2012-09-10 14:22:15 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > What format and information is needed?  I don't particularly like hard
> > coding information like this, but it should be doable.
> 
> passing the question on to Bug 842767 assignee, Shahar.
> [Shahar: This needs to be confirmed with Barak/Itamar, but I think we need
> information similar to the "clusterLevels" data being returned as part of
> the "getVdsCaps()" vdsm response (e.g. "['3.0', '3.1']")]
Today we have txt files in: /usr/share/rhev-hypervisor/
such as: 
version-6.3-20120607.0.txt
with one line that represent the version - such as:
6.3,20120607.0

I suggest to add another line with supported cluster versions comma seperated:
3.0,3.1

Comment 5 Mike Burns 2012-09-11 13:44:41 UTC
Relevant part of the diff:

@@ -55,6 +56,7 @@ mkdir %{buildroot}
 %{__install} -d -m0755 %{buildroot}%{app_root}
 %{__install} -p -m0644 %{image_iso} %{buildroot}%{app_root}/%{product_code}-%{version}-%{release}.iso
 echo %{version},%{release} > %{buildroot}%{app_root}/version-%{version}-%{release}.txt
+echo %{vdsm_compat} >> %{buildroot}%{app_root}/version-%{version}-%{release}.txt

 %post
 nvr=0

Comment 7 Mike Burns 2012-09-19 15:23:31 UTC
Reset to assigned -- this causes a rhevm crash when upgrading rhev-h

Comment 8 Mike Burns 2012-09-19 16:24:05 UTC
*** Bug 858249 has been marked as a duplicate of this bug. ***

Comment 9 Mike Burns 2012-10-12 13:07:58 UTC
committed change will be available in next build.

The compatibility will be added in a new file
vdsm-compatibility-%{version}-%{release}.iso

A symlink pointing to the latest will be created as well named:
vdsm-compatibility.txt

The format of this file is:

3.1,3.0

Comment 15 errata-xmlrpc 2013-02-28 18:58:11 UTC
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.

http://rhn.redhat.com/errata/RHSA-2013-0579.html


Note You need to log in before you can comment on or make changes to this bug.