Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1601307 - Logging installation failed at TASK [openshift_logging_fluentd : Label OCP nodes for Fluentd]
Logging installation failed at TASK [openshift_logging_fluentd : Label OCP no...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging (Show other bugs)
3.7.1
Unspecified Unspecified
medium Severity high
: ---
: 3.7.z
Assigned To: Jeff Cantrill
Anping Li
: Regression
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-07-15 23:08 EDT by Junqi Zhao
Modified: 2018-08-09 18:15 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Undefined variable in the fluentd role Consequence: The deployment failed trying to label the nodes Fix: Replaced variable with the correct one to the oc client binary Result: Logging deployment is possible and properly labels the nodes.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-08-09 18:14:04 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/9233 None None None 2018-07-17 10:28 EDT
Red Hat Product Errata RHBA-2018:2337 None None None 2018-08-09 18:15 EDT

  None (edit)
Description Junqi Zhao 2018-07-15 23:08:18 EDT
Description of problem:
Deploy logging 3.7, ansible threw out error

fatal: [###############]: FAILED! => {"failed": true, "msg": "the field 'args' has an invalid value, which appears to include a variable that is undefined. The error was: 'openshift_client_binary' is undefined\n\nThe error appears to have been in '/usr/share/ansible/openshift-ansible/roles/openshift_logging_fluentd/tasks/main.yaml': line 208, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n# We need to pause between nodes while labeling to avoid overloading the scheduler.\n- name: Label OCP nodes for Fluentd\n  ^ here\n"}

Version-Release number of selected component (if applicable):
openshift-ansible-3.7.58-1.git.37.6db1e6f.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1. Deploy logging 3.7
2.
3.

Actual results:
Logging installation failed at TASK [openshift_logging_fluentd : Label OCP nodes for Fluentd]

Expected results:
Installation is successfully

Additional info:
openshift_logging_install_logging=true
openshift_logging_image_prefix=${IMAGE_PREFIX}
openshift_logging_image_version=v3.7
Comment 1 Jeff Cantrill 2018-07-16 13:05:40 EDT
Please identify the version of ansible being used.
Comment 2 Junqi Zhao 2018-07-16 20:24:36 EDT
(In reply to Jeff Cantrill from comment #1)
> Please identify the version of ansible being used.

ansible-2.3.2.0-2.el7.noarch
Comment 4 Junqi Zhao 2018-07-17 20:21:34 EDT
Need new openshift-ansible package to verify this defect, the currently latest version is 3.7.59-1 which does not include the fix
Comment 6 Junqi Zhao 2018-07-30 21:54:23 EDT
Tested, logging could be installed successfully without error

# rpm -qa | grep ansible
openshift-ansible-lookup-plugins-3.7.61-1.git.0.36791ef.el7.noarch
openshift-ansible-3.7.61-1.git.0.36791ef.el7.noarch
openshift-ansible-filter-plugins-3.7.61-1.git.0.36791ef.el7.noarch
openshift-ansible-playbooks-3.7.61-1.git.0.36791ef.el7.noarch
openshift-ansible-callback-plugins-3.7.61-1.git.0.36791ef.el7.noarch
openshift-ansible-docs-3.7.61-1.git.0.36791ef.el7.noarch
ansible-2.3.2.0-2.el7.noarch
openshift-ansible-roles-3.7.61-1.git.0.36791ef.el7.noarch
Comment 8 errata-xmlrpc 2018-08-09 18:14:04 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.