Bug 1431935 - Ansible failed at TASK [openshift_logging : Generate Elasticsearch DeploymentConfig], 'es_pvc_pool' is undefined
Summary: Ansible failed at TASK [openshift_logging : Generate Elasticsearch Deployment...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Jeff Cantrill
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks: 1425312 1431527
TreeView+ depends on / blocked
 
Reported: 2017-03-14 05:18 UTC by Junqi Zhao
Modified: 2017-07-24 14:11 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-04-12 19:03:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
ansible running log, 'es_pvc_pool' is undefined (674.33 KB, text/plain)
2017-03-14 05:18 UTC, Junqi Zhao
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0903 0 normal SHIPPED_LIVE OpenShift Container Platform atomic-openshift-utils bug fix and enhancement 2017-04-12 22:45:42 UTC

Description Junqi Zhao 2017-03-14 05:18:03 UTC
Created attachment 1262773 [details]
ansible running log, 'es_pvc_pool' is undefined

Description of problem:

Deploy  logging stacks via ansible, it faild at TASK [openshift_logging : Generate Elasticsearch DeploymentConfig].

This defect blocks all installations now.

TASK [openshift_logging : Generate Elasticsearch DeploymentConfig] *************
task path: /usr/share/ansible/openshift-ansible/roles/openshift_logging/tasks/install_elasticsearch.yaml:37
fatal: [ec2-54-165-114-84.compute-1.amazonaws.com]: FAILED! => {
    "failed": true
}

MSG:

the field 'vars' has an invalid value, which appears to include a variable that is undefined. The error was: 'es_pvc_pool' is undefined

The error appears to have been in '/usr/share/ansible/openshift-ansible/roles/openshift_logging/tasks/install_elasticsearch.yaml': line 37, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:


- name: Generate Elasticsearch DeploymentConfig
  ^ here

    to retry, use: --limit @/usr/share/ansible/openshift-ansible/playbooks/common/openshift-cluster/openshift_logging.retry


Version-Release number of selected component (if applicable):
openshift-ansible-3.5.32-1.git.0.42cf266.el7.noarch
openshift-ansible-playbooks-3.5.32-1.git.0.42cf266.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1.Deploy logging stacks via ansible.
2.Check the deployment result

Actual results:
Deployment failed, failed at TASK [openshift_logging : Generate Elasticsearch DeploymentConfig]
Expected results:
Deployment should be successful

Additional info:
Ansible running log attached

Comment 1 Jeff Cantrill 2017-03-14 14:24:02 UTC
https://github.com/openshift/openshift-ansible/pull/3651

Please attach your inventory file in future.  This issue occurs because the openshift_logging_es_pvc_size is set to 'G' or some other value that does not begin with a number.

Comment 2 Junqi Zhao 2017-03-15 02:01:19 UTC
@Jeff,

Tested with your fix, this error does not exist now.

We need to have one new rpm package for openshift-ansible-playbooks.

openshift-ansible-playbooks version is still:openshift-ansible-playbooks-3.5.32-1.git.0.42cf266.el7.no, the same version as this defect was submitted.

Comment 4 Junqi Zhao 2017-03-16 02:10:18 UTC
Verified with the following versions, this defect is fixed.

openshift-ansible-3.5.35-1.git.0.7aa4728.el7.noarch
openshift-ansible-playbooks-3.5.35-1.git.0.7aa4728.el7.noarch

Comment 6 errata-xmlrpc 2017-04-12 19:03:51 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:0903


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