Bug 1480878

Summary:	Logging does not deploy dynamic PVC when volume size is not specified
Product:	OpenShift Container Platform	Reporter:	Nicholas Schuetz <nick>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.6.1	CC:	anli, aos-bugs, jcantril, rmeggins, sdodson
Target Milestone:	---
Target Release:	3.6.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: The installer does not default a value for PVC size Consequence: The storage provisoner is unable to bind a PV to the PVC for glusterfs because no requested size is provided. Fix: Default a value Result: The PVC is created using a default value when requesting a dynamic pvc	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-10-17 11:45:24 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 Nicholas Schuetz 2017-08-12 16:31:36 UTC

Description of problem:

when installing the metrics stack, if you dont specify a PVC size, it defaults to 10Gi and provisions just fine.

This:
ansible-playbook /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/openshift-metrics.yml -e openshift_metrics_install_metrics=True -e openshift_metrics_cassandra_storage_type=dynamic 

Gives you this:
pvc-8ec379c3-7f78-11e7-8aea-525400fb09ec   10Gi       RWO           Delete          Bound     openshift-infra/metrics-cassandra-1   glusterfs-storage             5m

Perfect.... however...

This:

ansible-playbook /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/openshift-logging.yml -e openshift_logging_install_logging=True -e openshift_logging_es_pvc_dynamic=True -e 

Gives you this:
Failed to provision volume with StorageClass "glusterfs-storage": glusterfs: create volume err: error creating volume Invalid volume size.


When you add another parameter to explicitly set the PVC size, like this:

 ansible-playbook /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/openshift-logging.yml -e openshift_logging_install_logging=True -e openshift_logging_es_pvc_dynamic=True -e openshift_logging_es_pvc_size=10Gi

You get this (a proper install):

pvc-6c03818e-7f7a-11e7-af65-525400fb09ec   10Gi       RWO           Delete          Bound     logging/logging-es-0                  glusterfs-storage             2m



There are too many inconsistencies between the metrics and the logging stacks and how they are configured.  This ultimately needs to be cleaned up....

-Nick

Comment 1 Jeff Cantrill 2017-08-23 18:58:11 UTC

https://github.com/openshift/openshift-ansible/pull/5184

Comment 2 Jeff Cantrill 2017-08-23 19:01:12 UTC

Fixed in 3.6 with: openshift-ansible/pull/5185

Comment 3 openshift-github-bot 2017-08-29 20:47:47 UTC

Commits pushed to master at https://github.com/openshift/openshift-ansible

https://github.com/openshift/openshift-ansible/commit/2ad64aeaffa23854ecf96bd903f5a5a9f1284ee0
bug 1480878. Default pvc for logging

https://github.com/openshift/openshift-ansible/commit/be513254b49822c18509debbd944437d1f93b162
Merge pull request #5184 from jcantrill/bz1480878_default_logging_pvc_size

bug 1480878. Default pvc for logging

Comment 4 Rich Megginson 2017-09-08 16:15:09 UTC

Has this been fixed in atomic-openshift-ansible for 3.6 or 3.7?  Can we move this to ON_QA?

Comment 6 Anping Li 2017-09-14 06:12:31 UTC

Using openshift-ansible-3.6.173.0.33., the pvc can be generated without openshift_logging_es_pvc_size.

But the fix is in openshift-ansible, and openshift-ansible packages is not  https://errata.devel.redhat.com/advisory/30362. We should open a new errata or attach to existing installer errata.

Comment 7 Anping Li 2017-09-21 11:30:49 UTC

@scott, The fix is in openshift-ansible. could you move this bug to the proper installer errata?

Comment 9 Scott Dodson 2017-09-21 12:39:13 UTC

sure

Comment 12 errata-xmlrpc 2017-10-17 11:45:24 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-2017:2900