Bug 1267540

Summary:	Missing requirement on otopi >= 1.4.0
Product:	[oVirt] ovirt-engine	Reporter:	Sandro Bonazzola <sbonazzo>
Component:	Packaging.rpm	Assignee:	Sandro Bonazzola <sbonazzo>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Matyáš <pmatyas>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	bugs, didi, lveyde, rmartins, sherold, stirabos
Target Milestone:	ovirt-3.6.0-ga	Keywords:	Automation
Target Release:	3.6.0	Flags:	rule-engine: ovirt-3.6.0+ rule-engine: exception+ sherold: planning_ack+ sbonazzo: devel_ack+ pnovotny: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/518/console
Whiteboard:	integration
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-04 11:43:32 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 Sandro Bonazzola 2015-09-30 11:09:15 UTC

Since a requirement on otopi >= 1.3.2 is in place, without a yum update ovirt-engine-3.6.0 can be installed with otopi-1.3.2 failing the setup with:

[ ERROR ] Failed to execute stage 'Environment setup': type object 'BaseEnv' has no attribute 'EXIT_CODE'

otopi-1.4.0 is required.

Detected by jenkins: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/518/console

Not marking as blocker since 'yum update "otopi*"' solve the issue.

Comment 1 Sandro Bonazzola 2015-11-04 11:43:32 UTC

oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.