Bug 1573877

Summary:	fluendt label not being set on nodes during scaleup
Product:	OpenShift Container Platform	Reporter:	Kim Borup <kborup>
Component:	Installer	Assignee:	Scott Dodson <sdodson>
Status:	CLOSED WONTFIX	QA Contact:	Johnny Liu <jialiu>
Severity:	low	Docs Contact:
Priority:	low
Version:	3.7.1	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	3.7.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-02 12:51:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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