Description of problem: This defect is split from https://bugzilla.redhat.com/show_bug.cgi?id=1561196#c15 Deploy logging firstly and change fluentd nodeSelector to non-default value, logging-infra-test-fluentd=true # oc get ds NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE logging-fluentd 2 2 2 2 2 logging-infra-test-fluentd=true 10m Update logging with the same inventory, fluentd nodeSelector would always use the default nodeSelector logging-infra-fluentd=true, not get the existing nodeSelector from environment # oc get ds NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE logging-fluentd 2 2 2 2 2 logging-infra-fluentd=true 15m Version-Release number of selected component (if applicable): # rpm -qa | grep openshift-ansible openshift-ansible-roles-3.9.27-1.git.0.52e35b5.el7.noarch openshift-ansible-docs-3.9.27-1.git.0.52e35b5.el7.noarch openshift-ansible-playbooks-3.9.27-1.git.0.52e35b5.el7.noarch openshift-ansible-3.9.27-1.git.0.52e35b5.el7.noarch How reproducible: Always Steps to Reproduce: 1. See the description part 2. 3. Actual results: Always use Expected results: Should use existing fluentd nodeSelector Additional info:
https://github.com/openshift/openshift-ansible/pull/8335
Tested with openshift-ansible-3.10.0-0.47.0.git.0.c018c8f.el7.noarch existing nodeselectors for fluentd could be used when update logging
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:1816