Bug 853092
| Summary: | rhev-h: supported vdsm compatibility versions should be supplied along with rhev-h ISOs | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Einav Cohen <ecohen> |
| Component: | rhev-hypervisor6 | Assignee: | Mike Burns <mburns> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.3 | CC: | cpelland, dyasny, gouyang, jboggs, leiwang, mburns, ovirt-maint, shavivi, ycui, ykaul |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-28 18:58:11 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: | 842767, 856827 | ||
|
Description
Einav Cohen
2012-08-30 13:39:12 UTC
What format and information is needed? I don't particularly like hard coding information like this, but it should be doable. (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']")] (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 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
Reset to assigned -- this causes a rhevm crash when upgrading rhev-h *** Bug 858249 has been marked as a duplicate of this bug. *** 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
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 |