Bug 1527569

Summary: openshift-ansible-playbook ignoring 'openshift_logging_storage_kind=nfs' in 3.7.14-1
Product: OpenShift Container Platform Reporter: Nicholas Schuetz <nick>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED WORKSFORME QA Contact: Anping Li <anli>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.7.1CC: aos-bugs, jokerman, mmccomas, pmcgowan, rmeggins
Target Milestone: ---   
Target Release: 3.7.z   
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-02-07 15:07:39 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:
Attachments:
Description Flags
complete ansible hosts file none

Description Nicholas Schuetz 2017-12-19 14:22:30 UTC
Created attachment 1370050 [details]
complete ansible hosts file

Description of problem:

When performing a new HA deployment(3.7.14-1.git.0.593a50e), metrics deploys just fine but logging does not.  Logging actually deploys, but it fails to mount ES on the external NFS export.

# oc get pv
NAME                             CAPACITY   ACCESSMODES   RECLAIMPOLICY   STATUS      CLAIM                                       STORAGECLASS   REASON    AGE
docker-registry-volume           20Gi       RWX           Retain          Bound       default/docker-registry-claim                                        30m
etcd-volume                      1Gi        RWO           Retain          Bound       openshift-ansible-service-broker/etcd                                30m
logging-volume                   10Gi       RWO           Retain          Available                                                                        30m
metrics-volume                   15Gi       RWO           Retain          Bound       openshift-infra/metrics-1                                            30m

The logging playbook never creates the PVC or attempts to mount it.  

Using these ansible host vars....

openshift_logging_install_logging=true
openshift_logging_storage_kind=nfs
openshift_logging_storage_access_modes=['ReadWriteOnce']
openshift_logging_storage_host=storage.home.nicknach.net
openshift_logging_storage_nfs_directory=/home/data/openshift/enterprise
openshift_logging_storage_volume_name=logging
openshift_logging_storage_volume_size=10Gi
openshift_logging_storage_labels={'storage':'logging'}

openshift_metrics_install_metrics=true
openshift_metrics_storage_kind=nfs
openshift_metrics_storage_access_modes=['ReadWriteOnce']
openshift_metrics_storage_host=storage.home.nicknach.net
openshift_metrics_storage_nfs_directory=/home/data/openshift/enterprise
openshift_metrics_storage_volume_name=metrics
openshift_metrics_storage_volume_size=15Gi
openshift_metrics_storage_labels={'storage':'metrics'}

It almost like it's ignoring 'openshift_logging_storage_kind=nfs'





Description of problem:

Version-Release number of the following components:
rpm -q openshift-ansible
rpm -q ansible
ansible --version

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated

Expected results:

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 1 Nicholas Schuetz 2018-02-06 22:17:46 UTC
Looks like this is now fixed in the latest puddle build.

[root@master01 ~]# oc get pv
NAME                             CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS    CLAIM                                       STORAGECLASS   REASON    AGE
docker-registry-volume           20Gi       RWX            Retain           Bound     default/docker-registry-claim                                        10m
etcd-volume                      1Gi        RWO            Retain           Bound     openshift-ansible-service-broker/etcd                                10m
logging-volume                   10Gi       RWO            Retain           Bound     logging/logging-es-0                                                 10m
metrics-volume                   15Gi       RWO            Retain           Bound     openshift-infra/metrics-cassandra-1                                  10m
prometheus-alertbuffer-volume    5Gi        RWO            Retain           Bound     openshift-metrics/prometheus-alertbuffer                             10m
prometheus-alertmanager-volume   6Gi        RWO            Retain           Bound     openshift-metrics/prometheus-alertmanager                            10m
prometheus-volume                7Gi        RWO            Retain           Bound     openshift-metrics/prometheus                                         10m

[root@master01 ~]# rpm -q atomic-openshift-master
atomic-openshift-master-3.9.0-0.38.0.git.0.9399bce.el7.x86_64

Comment 2 Jeff Cantrill 2018-02-07 15:07:39 UTC
Closing as WFM as there was no explicit fix or action taken which resolved