Bug 1737605 - Unable to install the ElasticSearch pod on openshift-logging using a defined StorageClass on the inventory
Summary: Unable to install the ElasticSearch pod on openshift-logging using a defined ...
Keywords:
Status: CLOSED DUPLICATE of bug 1732154
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.11.0
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Jeff Cantrill
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-05 20:19 UTC by Miguel Figueiredo Nunes
Modified: 2019-08-05 20:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-05 20:22:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.