Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1502022

Summary:	Update python-crypto to 2.6.1-16
Product:	Red Hat OpenStack	Reporter:	shreshtha joshi <shrjoshi>
Component:	python-crypto	Assignee:	shreshtha joshi <shrjoshi>
Status:	CLOSED ERRATA	QA Contact:	Shai Revivo <srevivo>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.0 (Kilo)	CC:	apevec, jjoyce, lhh, srevivo
Target Milestone:	zstream	Keywords:	Triaged, ZStream
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-crypto-2.6.1-16.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1501281	Environment:
Last Closed:	2017-11-15 13:25:06 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 shreshtha joshi 2017-10-13 18:23:00 UTC

+++ This bug was initially created as a clone of Bug #1501281 +++

Description of problem:

RHEL 7 Extras shipped a version of python-crypto for Ansible's usage which then superseded what existed in the OpenStack repositories. In order to preserve upgrade compatibility between OpenStack releases, we need to update python-crypto to an nvr >= the version in Extras.

Version-Release number of selected component (if applicable):
python-crypto-2.6.1-15.el7

How reproducible:
100%

Steps to Reproduce:
1. Enable Extras
2. 'yum update python-crypto'

Actual results: python-crypto is obtained from the Extras repository.


Expected results: python-crypto is obtained from the OpenStack repository.

Comment 4 errata-xmlrpc 2017-11-15 13:25:06 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://access.redhat.com/errata/RHBA-2017:3223