Bug 1159784

Summary:	[RFE] Document when and where new features are available when upgrading cluster / datacenters
Product:	[oVirt] ovirt-engine	Reporter:	Daniel Helgenberger <daniel.helgenberger>
Component:	Documentation	Assignee:	bugs <bugs>
Status:	CLOSED WONTFIX	QA Contact:	bugs <bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	---	CC:	adahms, bugs, lsurette, s.kieske, srevivo
Target Milestone:	---	Keywords:	Documentation, FutureFeature, Improvement
Target Release:	---	Flags:	ylavi: ovirt-future? rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-03 07:07:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Docs	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Daniel Helgenberger 2014-11-03 10:38:14 UTC

Document URL: 
http://www.ovirt.org/OVirt_3.5_Release_Notes

Section Number and Name: 
http://www.ovirt.org/OVirt_3.5_Release_Notes#Install_.2F_Upgrade_from_Previous_Versions

Describe the issue:
There is confusion when exactly new features are available after upgrading oVirt [1].
When a new oVirt version is released usually some new features require to have either the engine, the cluster and further the datacenter version upgraded. Right now, at least upgrading a datacenter is a non - reversible process witch some use cases might require to be postponed for later bugfix releases.  

Suggestions for improvement: 
In the new features section, add the requirement to be Engine|Cluster|Data Center. My reasoning is, there will be no combinations as they are really stages in the upgrade (a 3.5 DC requres 3.5 clusters; all of them require a 3.5 Engine) 

Additional information: 
[1] http://www.mail-archive.com/users@ovirt.org/msg22320.html

Comment 3 Casper (RHV QE bot) 2022-10-18 21:30:39 UTC

This bug has low overall severity and is not going to be further verified by QE. If you believe special care is required, feel free to properly align relevant severity, flags and keywords to raise PM_Score or use one of the Bumps ('PrioBumpField', 'PrioBumpGSS', 'PrioBumpPM', 'PrioBumpQA') in Keywords to raise it's PM_Score above verification threashold (1000).

Comment 4 Sandro Bonazzola 2023-08-03 07:07:39 UTC

No updates since the bug was opened 9 years ago, closing as won't fix.
If still relevant please open an issue on https://github.com/oVirt/ovirt-site/issues