Bug 1308593

Summary: redhat-support-tool should depend on python-magic
Product: Red Hat Enterprise Linux 6 Reporter: Filip Holec <fholec>
Component: redhat-support-toolAssignee: Mark Huth <mhuth>
Status: CLOSED ERRATA QA Contact: Petr Šplíchal <psplicha>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.8CC: kroberts, mhuth, ohudlick, psplicha, tlavigne
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-11 01:26:28 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:

Description Filip Holec 2016-02-15 15:03:54 UTC
Description of problem:
If there is fresh installation of redhat-support-tool - for example on our internal servers - and package python-magic is not installed, backtrace will appear. That package should be installed with redhat-support-tool (and *-lib-python as well).

Version-Release number of selected component (if applicable):
redhat-support-tool-0.9.8-3.el6

How reproducible:
Always

Steps to Reproduce:
1.redhat-support-tool diagnose /var/log/messages

Actual results:
Traceback (most recent call last):
  File "/usr/bin/redhat-support-tool", line 21, in <module>
    from redhat_support_tool.helpers.common import set_docstring
  File "/usr/lib/python2.6/site-packages/redhat_support_tool/helpers/common.py", line 25, in <module>
    from redhat_support_tool.helpers.soscleaner import SOSCleaner
  File "/usr/lib/python2.6/site-packages/redhat_support_tool/helpers/soscleaner.py", line 27, in <module>
    import magic
ImportError: No module named magic

Expected results:
Command passes without any problem

Additional info:
We should be able to fix and verify this issue in rhel-6.8 release.

Comment 10 errata-xmlrpc 2016-05-11 01:26:28 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0969.html