Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1549296 - openshift_logging_es_pvc_storage_class_name' is undefined, prevents logging from deploying
openshift_logging_es_pvc_storage_class_name' is undefined, prevents logging f...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging (Show other bugs)
3.7.1
All All
unspecified Severity high
: ---
: 3.7.z
Assigned To: Jeff Cantrill
Anping Li
: OpsBlocker
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-02-26 17:12 EST by Dan Yocum
Modified: 2018-04-05 05:40 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-05 05:39:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0636 None None None 2018-04-05 05:40 EDT

  None (edit)
Description Dan Yocum 2018-02-26 17:12:10 EST
Description of problem:

Using openshift-ansible-3.7.23-1.git.0.bc406aa.el7.noarch to deploy in either GCE or AWS, the following error is issued:

TASK [openshift_logging_elasticsearch : Creating ES storage template - static] *************************************************************
Monday 26 February 2018  16:48:15 -0500 (0:00:00.487)       0:02:27.148 ******* 
fatal: [18.219.244.29]: FAILED! => {"msg": "The field 'vars' has an invalid value, which includes an undefined variable. The error was: {{ o
penshift_logging_es_pvc_storage_class_name }}: 'openshift_logging_es_pvc_storage_class_name' is undefined\n\nThe error appears to have been 
in '/home/dyocum/git/openshift-tools/openshift/installer/vendored/openshift-ansible-3.7.23/roles/openshift_logging_elasticsearch/tasks/main.
yaml': line 330, column 7, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n
    # storageclasses with the storageClassName set to \"\" in pvc.j2\n    - name: Creating ES storage template - static\n      ^ here\n\nexc
eption type: <class 'ansible.errors.AnsibleUndefinedVariable'>\nexception: {{ openshift_logging_es_pvc_storage_class_name }}: 'openshift_log
ging_es_pvc_storage_class_name' is undefined"}





Version-Release number of selected component (if applicable):
ppenshift-ansible-3.7.23-1.git.0.bc406aa.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1. provision a cluster in AWS or GCE with logging

Actual results:
logging fails to deploy

Expected results:
logging is deployed

Additional info:


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 Dan Yocum 2018-02-26 17:13:28 EST
This used to work when using openshift-ansible-3.7.14.
Comment 2 ewolinet 2018-02-27 10:23:41 EST
This should be resolved as of openshift-ansible-3.7.24-1
Can you please test using that release?
Comment 3 Dan Yocum 2018-02-27 12:12:03 EST
I will test with the 3.7.31 candidate release and let you know.
Comment 4 Dan Yocum 2018-03-06 13:32:32 EST
I'm using o-a 3.7.35 candidate rpm and this is no longer an issue.
Comment 5 Peter Ruan 2018-03-06 17:13:46 EST
I can install logging via ansible using oc v3.7.36
Comment 9 errata-xmlrpc 2018-04-05 05:39:53 EDT
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-2018:0636

Note You need to log in before you can comment on or make changes to this bug.