Bug 1315828

Summary:	Current CentOS 7 builds of ovirt-node don't work on EFI hosts
Product:	[oVirt] ovirt-node	Reporter:	Shafer Stockton <shaferstockton>
Component:	Build	Assignee:	Ryan Barry <rbarry>
Status:	CLOSED NEXTRELEASE	QA Contact:	Ying Cui <ycui>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	3.6	CC:	bugs, fdeutsch
Target Milestone:	---	Flags:	rule-engine: planning_ack? fdeutsch: devel_ack+ rule-engine: testing_ack?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-22 09:37: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:

Description Shafer Stockton 2016-03-08 17:35:54 UTC

Description of problem:
The install errors out and says no such file or directory and fails to complete.


How reproducible:
Very reproducible.

Steps to Reproduce:
1. Boot CentOS 7 ovirt-node ISO on an EFI enabled host
2. Attempt to install
3. Get the error and install dies

Actual results:
Failure to install

Expected results:
Install completes

Additional info:
I spent some time digging in to this and determined that the /etc/system-release-cpe file was being set incorrectly. The centos7-post.ks file needs to be updated on line 108 to reflect centos instead of redhat. The $MAJORVER is also being set improperly, but I'm not sure where to tweak that.

If I boot the installer and start the rescue shell I can modify /etc/system-release-cpe. After I change it to reflect the correct distribution and major version number I can start the installer over and things complete as expected.

Comment 1 Red Hat Bugzilla Rules Engine 2016-03-09 09:52:36 UTC

Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 2 Fabian Deutsch 2016-03-22 09:37:40 UTC

This will be fixed in oVirt Node Next, expect a pre-release soon.