Bug 1508150
Summary: | If an existing PVC used by an Elasticsearch DC is not labeled with logging-infra=support a new PVC is created | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Peter Portante <pportant> |
Component: | Logging | Assignee: | ewolinet |
Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 3.6.1 | CC: | aos-bugs, ewolinet, jcantril, pdwyer, pportant, rmeggins |
Target Milestone: | --- | Keywords: | OpsBlocker |
Target Release: | 3.6.z | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: |
undefined
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-14 21:02:32 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
Peter Portante
2017-10-31 21:26:23 UTC
Using openshift-ansible v3.6.173.0.59. This is stemming from the fact that in 3.5 we pulled this information from the DC to populate the PVC name, in 3.6 we try to abstract that using logging_facts which requires a label instead of walking the DC to get the PVC name. @peter, How could we create a pvc named like logging-es-ek5tsdfc? What are the openshift-ansible version and inventory variables? Verified and pass with openshift-ansible-3.7.9-1.git.4.d445616.el7.noarch 1. Deploy logging 2. Create pvc named oc get pvc -o name persistentvolumeclaims/logging-es-ek5tsdfc persistentvolumeclaims/logging-es-tdxh1mh5 3. Attached the pvc to ES pods oc set volume dc/logging-es-data-master-stfcyny3 --add --overwrite --type=pvc --name=elasticsearch-storage --claim-name=logging-es-ek5tsdfc oc set volume dc/logging-es-ops-data-master-gfy26cki --add --overwrite --type=pvc --name=elasticsearch-storage --claim-name=logging-es-tdxh1mh5 4. Redeployed logging by playbook openshift_logging_es_pvc_dynamic=True openshift_logging_es_pvc_prefix=logging-es openshift_logging_es_ops_pvc_prefix=logging-es-ops 5. Check the pvc and dc The playbook wasn't create new pvc, the playbook is using the existing pvc. #oc get pvc -o name persistentvolumeclaims/logging-es-ek5tsdfc persistentvolumeclaims/logging-es-tdxh1mh5 ## oc get dc --selector logging-infra=elasticsearch -o yaml |grep -A 1 persistentVolumeClaim persistentVolumeClaim: claimName: logging-es-ek5tsdfc -- persistentVolumeClaim: claimName: logging-es-tdxh1mh5 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-2017:3438 |