Bug 1381756

Summary: Bug: python-dateutil has dependency on python-six rpm on RHEL6.8
Product: Red Hat Enterprise Linux 6 Reporter: BHUSHANGDANGRE <bdangre>
Component: python-dateutilAssignee: Charalampos Stratakis <cstratak>
Status: CLOSED ERRATA QA Contact: Jan Kepler <jkejda>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.8CC: bdangre, bnater, cstratak, hhorak, jkejda, redakkan, skallesh, vrjain
Target Milestone: rcFlags: cstratak: needinfo? (bdangre)
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: python-dateutil-1.4.1-7.el6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-21 10:45:45 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 BHUSHANGDANGRE 2016-10-04 22:48:59 UTC 
Description of problem:"subscription-manager --> pythom-rhsm-->python-dateutil-->six"

Version-Release number of selected component (if applicable):
RHEL6.8

Here is the details from the trace back from subscription-manager core dump.

parser.py:40:<module>:ImportError: No module named six <==== parser.py comes from python-dateutil package 

Traceback (most recent call last):
  File "/usr/libexec/rhsmcertd-worker", line 26, in <module> <===== rhsmcertd-worker comes from subscription-manager
    from rhsm import connection
  File "/usr/lib64/python2.6/site-packages/rhsm/connection.py", line 20, in <module> <==== it calls dateutil.parser 
    import dateutil.parser
  File "/usr/lib/python2.6/site-packages/dateutil/parser.py", line 40, in <module> <========== python-dateutil rpm
    from six import text_type, binary_type, integer_types
ImportError: No module named six
Comment 3 vritant 2016-10-06 14:03:20 UTC 
Could this be related to:
https://github.com/dateutil/dateutil/issues/6 ?
Comment 11 errata-xmlrpc 2017-03-21 10:45:45 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-2017-0692.html