Bug 1195333 - ioprocess path is hardcoded within the python bindings
Summary: ioprocess path is hardcoded within the python bindings
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-distribution
Classification: oVirt
Component: ioprocess
Version: ioprocess-0.15.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-3.6.1
: ioprocess-0.15.0
Assignee: Oved Ourfali
QA Contact: Petr Kubica
URL:
Whiteboard:
Depends On:
Blocks: 1163069
TreeView+ depends on / blocked
 
Reported: 2015-02-23 15:35 UTC by Simone Tiraboschi
Modified: 2016-02-11 11:55 UTC (History)
7 users (show)

Fixed In Version: ioprocess-0.15.0-4
Clone Of:
Environment:
Last Closed: 2016-02-11 11:55:08 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-3.6.z+
ylavi: planning_ack+
rule-engine: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 38167 0 None None None Never

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.
Note You need to log in before you can comment on or make changes to this bug.