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

Bug 1585762

Summary: [DOCS] log aggregation created pvcs start with name logging-es-0 and not logging-es-1
Product: OpenShift Container Platform Reporter: Jatan Malde <jmalde>
Component: DocumentationAssignee: Michael Burke <mburke>
Status: CLOSED CURRENTRELEASE QA Contact: Anping Li <anli>
Severity: unspecified Docs Contact: Vikram Goyal <vigoyal>
Priority: unspecified    
Version: 3.7.1CC: anli, aos-bugs, jokerman, mark.vinkx, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-09 20:00:34 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 Jatan Malde 2018-06-04 16:19:59 UTC
Document URL: 

https://docs.openshift.com/container-platform/3.7/install_config/aggregate_logging.html#aggregated-elasticsearch

Section Number and Name: 

Persistent Elasticsearch Storage

Describe the issue: 

In https://docs.openshift.com/container-platform/3.7/install_config/aggregate_logging.html#aggregated-elasticsearch

says auto created pvcs are called logging-es-1, logging-es-2, and so on but

in reality they are created starting with logging-es-0. 


Suggestions for improvement: 

Please change it to logging-es-0, logging-es-1, logging-es-2 and so on.

Additional information: 

Also, the default  prefix is not `logging-es-` but `logging-es` because otherwise pvc with name logging-es--0 is created

Comment 2 Anping Li 2018-07-06 10:15:27 UTC
LGTM