Bug 829642

Summary:	engine-setup will not complete due to missing dependencies on Fedora 17 'Minimal' install
Product:	[Fedora] Fedora	Reporter:	DaGeek <gspurgeon>
Component:	ovirt-engine	Assignee:	Juan Hernández <juan.hernandez>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	high
Version:	17	CC:	acathrow, dbmacartney, dyasny, gspurgeon, iheim, juan.hernandez, mgoldboi, ykaul
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-16 23:58:29 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:

Description DaGeek 2012-06-07 08:07:54 UTC

Description of problem:

If you do a Fedora17 'minimal' install the install will crash when I tries to run /usr/sbin/semanage command that is not installed by the minimal setup. you will need to 1st need to run 'yum install policycoreutils-python'. Without this extra package the engine-setup command will fail with a fatal error.

This is the 2nd error in the engine-setup script, the 1st error seems to be a non-fatal error, where the script will try to run /usr/bin/nslookup that again is not installed by the 'minimal' install option.

The .rpm should have policycoreutils-python & nslookup also set as dependencies.

Version-Release number of selected component (if applicable):
Fedora 17 - x86_64
oVirt-engine - 3.0.0

How reproducible:

Steps to Reproduce:
1. Clean 'Minimal' install of Fedora 17
2. yum install ovirt-engine
3. engine-setup
  
Actual results:

Error when the setup script tries to run /usr/sbin/semanage 

Expected results:

fully installed & configured oVirt-engine

Additional info:

Comment 1 Juan Hernández 2012-06-07 14:46:28 UTC

In 3.1 the policycoreutils-python and nslookup are dependencies of the ovirt package, so this is solved there already.

I am fixing the official Fedora 3.0 package.

Comment 2 DaGeek 2012-06-07 15:00:26 UTC

Thanks for your help Juan

I assume there is no Public release date for 3.1 yet ?

Comment 3 Juan Hernández 2012-06-07 15:11:26 UTC

Feature freeze for 3.1 is today (Jun 7) and according to the project release policies the release is 30 days after feature freeze for the first 3 releases, so you can expect the upstream release in a month from now. Of course this is subject to change.

The official Fedora package will follow shortly after the upstream release.

Comment 4 Juan Hernández 2012-06-07 15:12:21 UTC

More details on the release policies are here:

http://www.ovirt.org/wiki/Release_Process

Comment 5 Fedora Update System 2012-06-07 15:40:44 UTC

ovirt-engine-3.0.0.0001-13.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/ovirt-engine-3.0.0.0001-13.fc17

Comment 6 Fedora Update System 2012-06-09 00:03:50 UTC

Package ovirt-engine-3.0.0.0001-13.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ovirt-engine-3.0.0.0001-13.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-9133/ovirt-engine-3.0.0.0001-13.fc17
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2012-06-16 23:58:29 UTC

ovirt-engine-3.0.0.0001-13.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.