Bug 1566058

Summary: [OSP13] Drop runtime requirement for python-crypto (heat)
Product: Red Hat OpenStack Reporter: Lon Hohberger <lhh>
Component: openstack-heatAssignee: Lon Hohberger <lhh>
Status: CLOSED ERRATA QA Contact: Ronnie Rasouli <rrasouli>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: jjoyce, jschluet, mburns, nlevinki, rhel-osp-director-maint, sbaker, shardy, slinaber, srevivo, tvignaud
Target Milestone: betaKeywords: EasyFix, Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: openstack-heat-10.0.1-0.20180411125639.825731d.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1566044 Environment:
Last Closed: 2018-06-27 13:50:58 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:
Bug Depends On:    
Bug Blocks: 1566065    

Description Lon Hohberger 2018-04-11 12:43:20 UTC
+++ This bug was initially created as a clone of Bug #1566044 +++

Description of problem:

openstack-heat-common has a hard dependency on python-crypto.

* As of, python-crypto is not required

* python-crypto hasn't been maintained in years upstream.

Version-Release number of selected component (if applicable): openstack-heat-10.0.1-0.20180404165313.825731d.el7ost

How reproducible: 100%

Steps to Reproduce:
1. yum install openstack-heat-common

Actual results:
  python-crypto is installed as well

Expected results:
  python-crypto is not installed

Additional info:
  Python-crypto has not been audited for FIPS compliance.

Comment 4 Ronnie Rasouli 2018-05-23 07:45:56 UTC
verified with openstack-heat-common-10.0.1-0.20180411125639.825731d.el7ost.noarch the python-crypto isn't installed

Comment 6 errata-xmlrpc 2018-06-27 13:50:58 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.