Bug 791283

Summary:	[RFE] Oz should automatically support new OS releases unless a special case is needed
Product:	[Retired] CloudForms Cloud Engine	Reporter:	Brad P. Crochet <brad>
Component:	oz	Assignee:	Ian McLeod <imcleod>
Status:	CLOSED EOL	QA Contact:	Dave Johnson <dajohnso>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.0.0	CC:	brad, clalancette, hbrock, morazi, nobody, whayutin
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-27 18:39:28 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Brad P. Crochet 2012-02-16 16:27:25 UTC

Description of problem:
Currently, Oz requires an update any time a new OS minor version is released.

Perhaps instead of enabling each release individually, the ones that need a special case should be handled as needed? And handle the others with sane defaults? I think that would make for less (unnecessary) updates to Oz, and allow testing to occur easily ahead of time to find out if something does indeed need to be a special case.                        

Version-Release number of selected component (if applicable):
oz-0.8.0-4.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. As of now, try to install RHEL 5.8. It fails.

Comment 1 wes hayutin 2012-02-16 16:30:19 UTC

With the exception of EC2 which requires an errata update to the jeos image rpms.

We need to be able to qualify upcoming releases of RHEL as a client in cloud forms. So we're hoping that private providers like vsphere and rhevm can build upcoming releases.

Thanks

Comment 2 wes hayutin 2012-02-22 23:46:59 UTC

moving version to 1.0.0 .  version = found in version

Comment 4 Hugh Brock 2012-02-27 17:20:16 UTC

Ian, can you comment please? Wes is suggesting that an errata should only be required to build RHEL for public providers. If this is easy, please dev-ack and fix; if not please move to 1.1.0.

Comment 5 Hugh Brock 2012-03-07 18:20:23 UTC

Moving to 1.1.0.

Comment 6 Mike Orazi 2012-08-09 15:31:38 UTC

Moving to 2.0.0? for consideration.

Comment 7 Chris Lalancette 2012-08-20 13:00:14 UTC

I agree that having to update Oz for every minor release isn't ideal.  The reason we have to update Oz for every Fedora release is that anaconda frequently makes backwards-incompatible changes that require code changes.

For RHEL, this is much less of a worry.  In fact, as it currently stands I have no known cases of RHEL breaking anaconda within a stable release series.  I would certainly accept patches that made this "just work" for RHEL, without any further Oz updates.

Chris