Bug 1573877 - fluendt label not being set on nodes during scaleup
Summary: fluendt label not being set on nodes during scaleup
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.7.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 3.7.z
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-02 12:23 UTC by Kim Borup
Modified: 2018-05-02 12:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-02 12:51:18 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Kim Borup 2018-05-02 12:23:52 UTC
Description of problem:
When running /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-node/scaleup.yml, you manually have to set the node label fluentd=true on the node after scaleup in order for fluentd to deploy to it.

Version-Release number of the following components:
 3.7.44

How reproducible:
All the time

Steps to Reproduce:
1. Install Openshift 
2. Add a node to new_nodes 
3. run scaleup for nodes.
4. check node labels

Actual results:
fluentd=true missing from node

Expected results:
during a scaleup the scaleup playbook should check the master configuration and if logging is enabled set the logging label so fluentd gets deployed on new nodes. 

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

Comment 1 Scott Dodson 2018-05-02 12:51:18 UTC
I agree this is how it should work but I don't think we'll get to fix this. Feel free to open a pull request with implementation if you have time to do so.

Comment 2 Scott Dodson 2018-05-02 12:51:51 UTC
Workaround: `oc label node/new-node.example.com fluentd=true` post scaleup


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