Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 986153

Summary:	Always run beah in Python 2.6+
Product:	[Retired] Beaker	Reporter:	Nick Coghlan <ncoghlan>
Component:	beah	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.13	CC:	aigao, asaha, dcallagh, dhoward, ebaak, jburke, pbunyan, plougher, qwan, tools-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	922252	Environment:
Last Closed:	2015-03-30 07:53:10 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:
Bug Depends On:	810893
Bug Blocks:	922252

Description Nick Coghlan 2013-07-19 05:32:26 UTC

Currently, we run beah in the system Python for RHEL 4+. For RHEL 3, we instead run it in a separately packaged version of Python 2.6.

This appears to be the cause of at least one bug when running in Python 2.3 on RHEL 4, and also prevents the use of more recent versions of Twisted on RHEL 5 (as RHEL 5 only provides Python 2.4, which was last supported in Twisted 11.0. At time of writing, the latest version of Twisted is 13.1).

This issue covers switching to using separately packaged versions of Python and other dependencies on RHEL 4 and RHEL 5 as well as on RHEL 3.

This change will mean that beah will always run in at least Python 2.6 (since the system Python in RHEL 6 is also 2.6) and may run in Python 2.7 (as that is the system Python in Fedora and RHEL 7+).

Comment 1 Nick Coghlan 2013-10-01 07:05:54 UTC

Switched order of dependency relative to bug 810893, since running on an upstream Twisted in an alternative harness is lower impact than always running on a system independent Python installation

Comment 3 Dan Callaghan 2015-03-30 07:53:10 UTC

At this point I think it makes more sense to focus on improving restraint instead.