Bug 1829765

Summary:	Unable to set report_discard_supported for cinder in RHSOP-13
Product:	Red Hat OpenStack	Reporter:	Srinivas Atmakuri <satmakur>
Component:	puppet-cinder	Assignee:	Alan Bishop <abishop>
Status:	CLOSED ERRATA	QA Contact:	Tzach Shefi <tshefi>
Severity:	medium	Docs Contact:	Chuck Copello <ccopello>
Priority:	low
Version:	13.0 (Queens)	CC:	abishop, jjoyce, jschluet, mariel, slinaber, tvignaud
Target Milestone:	z12	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	puppet-cinder-12.4.1-6.el7ost	Doc Type:	Bug Fix
Doc Text:	Before this update, the cinder RBD driver did not perform trim or discard operations, which prevented users from trimming unused spaces from cinder RBD volumes. With this update, the cinder RBD driver now supports trim and discard operations.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-24 11:33:20 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 Srinivas Atmakuri 2020-04-30 09:46:14 UTC

When deploying the tripleo, the cinder.conf setting "report_discard_supported" should be set true to enable the use of discard (trim/unmap).

Request to backport the below BZ for RHOSP-13.,
https://bugzilla.redhat.com/show_bug.cgi?id=1566619

Comment 9 Tzach Shefi 2020-06-09 17:05:24 UTC

Verified on:
puppet-cinder-12.4.1-7.el7ost.noarch

With an RBD backed system we see the report_discard_supported parameter indeed is set to true. 

[root@controller-0 ~]# grep report_discard /var/lib/config-data/puppet-generated/cinder/etc/cinder/cinder.conf 
#report_discard_supported = false
#report_discard_supported = false
report_discard_supported=True

Comment 11 errata-xmlrpc 2020-06-24 11:33:20 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-2020:2718