Bug 1195333

Summary:	ioprocess path is hardcoded within the python bindings
Product:	[oVirt] ovirt-distribution	Reporter:	Simone Tiraboschi <stirabos>
Component:	ioprocess	Assignee:	Oved Ourfali <oourfali>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Kubica <pkubica>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	ioprocess-0.15.0	CC:	amureini, bazulay, bugs, gklein, oourfali, pstehlik, sbonazzo
Target Milestone:	ovirt-3.6.1	Keywords:	CodeChange
Target Release:	ioprocess-0.15.0	Flags:	rule-engine: ovirt-3.6.z+ ylavi: planning_ack+ rule-engine: devel_ack+ pstehlik: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ioprocess-0.15.0-4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-11 11:55:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1163069

Description Simone Tiraboschi 2015-02-23 15:35:07 UTC

Description of problem:
ioprocess path it's hardcoded within the python bindings by:
 EXT_IOPROCESS = "/usr/libexec/ioprocess"
On different distribution/architecture it could be necessary to deploy it on a different path so it would be better to make it configurable at build time.

Version-Release number of selected component (if applicable):
0.15

How reproducible:
100% 

Steps to Reproduce:
1. check the code


Actual results:
 EXT_IOPROCESS is hardcoded to "/usr/libexec/ioprocess"

Expected results:
 EXT_IOPROCESS can be configured at build time.

Comment 1 Oved Ourfali 2015-11-11 16:39:07 UTC

This wasn't in the 3.6.0 ioprocess build. 
Will be in 3.6.1.

Comment 2 Red Hat Bugzilla Rules Engine 2015-11-11 16:39:09 UTC

This bug is marked for z-stream, yet the milestone is for a major version, therefore the milestone has been reset.
Please set the correct milestone or drop the z stream flag.

Comment 3 Red Hat Bugzilla Rules Engine 2015-11-11 16:39:09 UTC

Fixed bug tickets must have target milestone set prior to fixing them. Please set the correct milestone and move the bugs back to the previous status after this is corrected.

Comment 4 Red Hat Bugzilla Rules Engine 2015-11-11 16:39:09 UTC

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 6 Pavel Stehlik 2016-02-11 11:55:08 UTC

CodeChange, nothing for QE.