Description of problem: The pod should be redeployed once the nodeSelector is changed in CLO CR. That is the following of a https://bugzilla.redhat.com/show_bug.cgi?id=1694097 Version-Release number of selected component (if applicable): 4.x How reproducible: Always Steps to Reproduce: 1. Deploy cluster logging via cluster-logging-operator 2. Provide instance CR oc create -f https://github.com/openshift-qe/v3-testfiles/blob/master/logging/clusterlogging/nodeSelector.yaml 3. Change the nodeSelector in CR. For example: change the fluentd nodeSelector from logging=fluentd to logging=fluentd1 For example: change the kibana nodeSelector from logging=kibana to logging=kibana1 Actual results: The clusterlogging pods aren't redeployed. Expected results: The clusterlogging pods are redeployed. Additional info:
Closing in favor of https://bugzilla.redhat.com/show_bug.cgi?id=1694097 as work is required in both operators to support the fix *** This bug has been marked as a duplicate of bug 1694097 ***
https://github.com/openshift/cluster-logging-operator/pull/143
https://github.com/openshift/elasticsearch-operator/pull/116
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-2019:0758