Bug 1254644

Summary: ipsilon-client-install fails with ImportError: No module named requests
Product: Red Hat Enterprise Linux 7 Reporter: Jan Pazdziora (Red Hat) <jpazdziora>
Component: ipsilonAssignee: Rob Crittenden <rcritten>
Status: CLOSED ERRATA QA Contact: Namita Soman <nsoman>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 7.2CC: extras-qa, jpazdziora, ovasik, puiterwijk, spoore, ssorce
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipsilon-1.0.0-7.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1250566 Environment:
Last Closed: 2015-11-19 10:50:30 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:
Bug Depends On: 1250566    
Bug Blocks:    

Description Jan Pazdziora (Red Hat) 2015-08-18 14:44:42 UTC
+++ This bug was initially created as a clone of Bug #1250566 +++

Description of problem:

When running ipsilon-client-install, it fails because requests is not available.

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

# rpm -qf /usr/bin/ipsilon-client-install
ipsilon-client-1.0.0-1.fc22.noarch

How reproducible:

Deterministic.

Steps to Reproduce:
1. dnf install /usr/bin/ipsilon-client-install ipsilon-saml2 httpd mod_ssl
2. ipsilon-client-install --saml-idp-metadata https://idp.example.test/idp/saml2/metadata --saml-auth /protected

Actual results:

Traceback (most recent call last):
  File "/usr/bin/ipsilon-client-install", line 18, in <module>
    import requests
ImportError: No module named requests

Expected results:

/usr/lib/python2.7/site-packages/requests/packages/urllib3/connection.py:251: SecurityWarning: Certificate has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/shazow/urllib3/issues/497 for details.)
  SecurityWarning
Generating a 2048 bit RSA private key
....+++
...........+++
writing new private key to '/etc/httpd/saml2/nec-em12.rhts.eng.bos.redhat.com/certificate.key'
-----

Additional info:

Manually installing python-requests helps but we should not need to do that.

Comment 4 Scott Poore 2015-10-14 17:25:21 UTC
Verified.

Version ::

ipsilon-client-1.0.0-12.el7.noarch
python-requests-2.6.0-4.el7.noarch

Results ::

[root@rhel7-5 yum.repos.d]# yum remove python-requests
Loaded plugins: product-id, search-disabled-repos, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Resolving Dependencies
...
Erasing    : python-requests-2.6.0-4.el7.noarch                                                17/17 
...
Removed:
  python-requests.noarch 0:2.6.0-4.el7                                                                 
...


[root@rhel7-5 yum.repos.d]# yum install ipsilon-client
Loaded plugins: product-id, search-disabled-repos, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Resolving Dependencies
--> Running transaction check
---> Package ipsilon-client.noarch 0:1.0.0-12.el7 will be installed
--> Processing Dependency: ipsilon-filesystem = 1.0.0-12.el7 for package: ipsilon-client-1.0.0-12.el7.noarch
--> Processing Dependency: ipsilon-saml2-base = 1.0.0-12.el7 for package: ipsilon-client-1.0.0-12.el7.noarch
--> Processing Dependency: mod_auth_mellon for package: ipsilon-client-1.0.0-12.el7.noarch
--> Processing Dependency: python-requests for package: ipsilon-client-1.0.0-12.el7.noarch
...
---> Package python-requests.noarch 0:2.6.0-4.el7 will be installed
...
Complete!

[root@rhel7-5 yum.repos.d]# rpm -q ipsilon-client python-requests
ipsilon-client-1.0.0-12.el7.noarch
python-requests-2.6.0-4.el7.noarch
[root@rhel7-5 yum.repos.d]#

Comment 5 errata-xmlrpc 2015-11-19 10:50:30 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/RHEA-2015-2319.html