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

Bug 1644020

Summary:	[OSP13][Deployment] Backport tripleo support for nova:libvirt:use_volume_multipath
Product:	Red Hat OpenStack	Reporter:	Rajini Karthik <rajini.karthik>
Component:	openstack-tripleo-heat-templates	Assignee:	Martin Schuppert <mschuppe>
Status:	CLOSED ERRATA	QA Contact:	OSP DFG:Compute <osp-dfg-compute>
Severity:	high	Docs Contact:
Priority:	medium
Version:	13.0 (Queens)	CC:	arkady_kanevsky, cdevine, chadd, christopher_dearborn, david_paterson, dcadzow, dcain, gael_rehault, jschluet, jslagle, kurt_hey, lyarwood, mariel, mburns, morazi, mschuppe, owalsh, rajini.karthik
Target Milestone:	z4	Keywords:	FeatureBackport, Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-8.0.7-13.el7ost	Doc Type:	Enhancement
Doc Text:	This feature adds a new parameter `NovaLibvirtVolumeUseMultipath` (boolean), which sets the multipath configuration parameter `libvirt/volume_use_multipath` in the nova.conf file for Compute nodes. This parameter can be set for each Compute role. Default value is `False`.	Story Points:	---
Clone Of:
Clones:	1645489 (view as bug list)		Environment:
Last Closed:	2019-01-16 17:55:05 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:	1644018, 1645487
Bug Blocks:	1644017

Description Rajini Karthik 2018-10-29 18:45:35 UTC

Description of problem:
Backport tripleo support for nova:libvirt:use_volume_multipath
https://review.openstack.org/#/c/611655/

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 16 errata-xmlrpc 2019-01-16 17:55:05 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-2019:0068