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

Bug 1547323

Summary:	backport of Adding support for rpc_response_timeout in cinder conf
Product:	Red Hat OpenStack	Reporter:	PURANDHAR SAIRAM MANNIDI <pmannidi>
Component:	puppet-cinder	Assignee:	Alan Bishop <abishop>
Status:	CLOSED ERRATA	QA Contact:	Avi Avraham <aavraham>
Severity:	medium	Docs Contact:	Kim Nylander <knylande>
Priority:	medium
Version:	10.0 (Newton)	CC:	cschwede, dcadzow, jjoyce, jschluet, pablo.iranzo, slinaber, tshefi, tvignaud
Target Milestone:	z8	Keywords:	FeatureBackport, Triaged, ZStream
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	puppet-cinder-9.5.0-6.el7ost	Doc Type:	Enhancement
Doc Text:	This feature adds the rpc_response_timeout option to the /etc/cinder/cinder.conf file. This adds the ability to configure Cinder's RPC response timeout.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-17 15:48:40 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 PURANDHAR SAIRAM MANNIDI 2018-02-21 00:27:16 UTC

Description of problem:

backport of Adding support for rpc_response_timeout in cinder conf

Version-Release number of selected component (if applicable):
Red Hat OpenStack Platform 10


Additional Info:

https://review.openstack.org/#/c/426619/

Comment 10 Tzach Shefi 2018-04-29 10:24:15 UTC

Verified on:
puppet-cinder-9.5.0-6.el7ost.noarch

On /usr/share/openstack-puppet/modules/cinder/manifests/init.pp
Code has landed been included. 
#[*rpc_response_timeout*]
#(optional) Seconds to wait for a response from a call
# Defaults to $::os_service_default
rpc

Also cinder.conf
# Seconds to wait for a response from a call. (integer value)
#rpc_response_timeout = 60

Comment 13 errata-xmlrpc 2018-05-17 15:48:40 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-2018:1597