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

Bug 1737605

Summary:	Unable to install the ElasticSearch pod on openshift-logging using a defined StorageClass on the inventory
Product:	OpenShift Container Platform	Reporter:	Miguel Figueiredo Nunes <mnunes>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED DUPLICATE	QA Contact:	Anping Li <anli>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.11.0	CC:	aos-bugs, rmeggins
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-05 20:22:25 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 Miguel Figueiredo Nunes 2019-08-05 20:19:08 UTC

Description of problem:
Customer unable to create a dynamic pvc on the logging installation pointing to a specific StorageClass. Only able to install it dynamic using a specific StorageClass if it's for a  separated ops ES pod


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


How reproducible:


Steps to Reproduce:
1. Set on the inventory a specific StorageClass
1. Install the Openshift-logging component
2. Check if the Dynamic Persist Volume was created for ES.


Actual results:
PV/PVC not created to a specific Storage class dynamically. The customer used an workaround forcing the glusterblock StorageClass as the default StorageClass.

Expected results:
Be able to install the ES for apps using a defined StorageClass in the inventory.


Additional info:

Comment 4 Jeff Cantrill 2019-08-05 20:22:25 UTC


*** This bug has been marked as a duplicate of bug 1732154 ***