Bug 916158

Summary: fail2ban-client fails when run using sudo
Product: [Fedora] Fedora Reporter: Jan Včelák <jv+fedora>
Component: fail2banAssignee: Axel Thimm <axel.thimm>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: axel.thimm, jonathan.underwood, orion
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-16 14:56:37 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 Jan Včelák 2013-02-27 12:39:39 UTC
Description of problem:

fail2ban-client cannot be run via sudo without specifing the full path to the script.


Version-Release number of selected component (if applicable):
fail2ban-0.8.8-2.fc18.noarch

How reproducible:
always


Steps to Reproduce:
1. sudo fail2ban-client
2.
3.
  
Actual results:

$ sudo fail2ban-client 
Traceback (most recent call last):
  File "/bin/fail2ban-client", line 35, in <module>
    from common.version import version
ImportError: No module named common.version

Expected results:

fail2ban-client won't crash and will start.


Additional info:

Works fine when full path is specified:

$ sudo /usr/bin/fail2ban-client
Usage: /usr/bin/fail2ban-client [OPTIONS] <COMMAND>
...

Comment 1 Orion Poplawski 2013-03-16 14:56:37 UTC

*** This bug has been marked as a duplicate of bug 892365 ***