Bug 1346385

Summary: Update to 3.7.1
Product: Red Hat OpenStack Reporter: Lee Yarwood <lyarwood>
Component: python-oslo-concurrencyAssignee: Victor Stinner <vstinner>
Status: CLOSED ERRATA QA Contact: Ofer Blaut <oblaut>
Severity: high Docs Contact:
Priority: high    
Version: 9.0 (Mitaka)CC: apevec, ddomingo, jjoyce, lhh, mburns, nlevinki
Target Milestone: gaKeywords: Rebase
Target Release: 9.0 (Mitaka)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: python-oslo-concurrency-3.7.1-1.el7ost Doc Type: If docs needed, set a value
Doc Text:
This release includes updates from oslo.concurrency 3.7.1, which places new process limits required to address security vulnerability CVE-2015-5162. See https://bugs.launchpad.net/ossa/+bug/1449062 for details about the vulnerability and fix.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-11 12:25: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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1328957    

Description Lee Yarwood 2016-06-14 16:21:25 UTC
Description of problem:

The upcoming Nova rebase to 13.1.0 introduces a new requirement of oslo.concurrency>=3.7.1 via the following backport into stable/mitaka :

virt: set address space & CPU time limits when running qemu-img
https://review.openstack.org/#/c/326327/

Version-Release number of selected component (if applicable):
python-oslo-concurrency-3.6.1-0.20160229183723.7cd7883.el7ost

How reproducible:
N/A

Steps to Reproduce:
N/A

Actual results:
N/A

Expected results:
N/A

Additional info:
N/A

Comment 2 Ofer Blaut 2016-07-03 07:30:01 UTC
rpm is updated - python-oslo-concurrency-3.7.1-1.el7ost.noarch
cluster is running and VM are working

Comment 4 errata-xmlrpc 2016-08-11 12:25: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/RHEA-2016-1597.html