Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1601606 - openshift logging Ansible playbook installation while defining PVC manifest a match label selector should use value 'true' in quotes to avoid it to understandable as a Boolean value.
openshift logging Ansible playbook installation while defining PVC manifest a...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging (Show other bugs)
3.7.0
Unspecified Linux
unspecified Severity medium
: ---
: 3.7.z
Assigned To: Jeff Cantrill
Qiaoling Tang
:
Depends On: 1597282
Blocks: 1601605
  Show dependency treegraph
 
Reported: 2018-07-16 16:42 EDT by Jeff Cantrill
Modified: 2018-08-09 18:15 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: 1597282
Environment:
Last Closed: 2018-08-09 18:14:55 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
Github openshift/openshift-ansible/pull/9221 None None None 2018-07-16 16:42 EDT
Github openshift/openshift-ansible/pull/9223 None None None 2018-07-16 16:46 EDT
Red Hat Product Errata RHBA-2018:2337 None None None 2018-08-09 18:15 EDT

  None (edit)
Description Jeff Cantrill 2018-07-16 16:42:05 EDT
+++ This bug was initially created as a clone of Bug #1597282 +++

Description of problem:

Open shift logging installation via Ansible playbook with parameter openshift_logging_es_pv_selector={"logging-es":"true"} failed


Version-Release number of selected component (if applicable): 3.7 


How reproducible:

Host file entry:

openshift_logging_es_pv_selector={"logging-es":"true"}


Steps to Reproduce:
1. Inject openshift_logging_es_pv_selector={"logging-es":"true"} in Host file
2. ansible-playbook -i host /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/openshift-logging.yml


Actual results:
Installation successful 


Expected results:

"stderr": "Error from server (BadRequest): error when creating \"/tmp/openshift-logging-ansible-JGyENQ/templates/logging-es-pvc.yml\": PersistentVolumeClaim in version \"v1\" cannot be handled as a PersistentVolumeClaim: [pos 276]: json: expect char '\"' but got char '1'\n",


Additional info:

- Ansible create PVC manifest a match label selector value true without quotes.
- The value 'true' should be in quotes to avoid it to understandable as a Boolean value.

--- Additional comment from markv on 2018-07-02 09:54:32 EDT ---

The same problem with numeric values

--- Additional comment from Jeff Cantrill on 2018-07-11 16:46:40 EDT ---

Please provide the version of ansible where you saw this failure.
Comment 2 giriraj rajawat 2018-07-23 09:24:53 EDT
Ansible version

[root@osclu-pew01-m01 ~]# yum list  installed | grep -i ansible
Repodata is over 2 weeks old. Install yum-cron? Or run: yum makecache fast
ansible.noarch                    2.4.2.0-2.el7              @rhel-7-server-extras-rpms
openshift-ansible.noarch          3.7.46-1.git.0.37f607e.el7 @rhel-7-server-ose-3.7-rpms
openshift-ansible-callback-plugins.noarch
openshift-ansible-docs.noarch     3.7.46-1.git.0.37f607e.el7 @rhel-7-server-ose-3.7-rpms
openshift-ansible-filter-plugins.noarch
openshift-ansible-lookup-plugins.noarch
openshift-ansible-playbooks.noarch
openshift-ansible-roles.noarch    3.7.46-1.git.0.37f607e.el7 @rhel-7-server-ose-3.7-rpms
Comment 4 Qiaoling Tang 2018-08-03 01:57:48 EDT
Verified on ose-ansible v3.7.61-1. Logging deployed successfully with openshift_logging_es_pv_selector={"logging-es":"true"} set in inventory file.
Comment 6 errata-xmlrpc 2018-08-09 18:14:55 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:2337

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