Description of problem: As a admin of openshift cluster, I want to the logging pod can be rescheduled once I change the ndoeSelector in clusterlogging resource file 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 nodeSelector to logging=es2. Actual results: The clusterlogging pods aren't redeployed. Expected results: The clusterlogging pods are redeployed. Additional info:
right - you have to set the clusterlogging managementState to Unmanaged
https://github.com/openshift/elasticsearch-operator/pull/114
https://github.com/openshift/cluster-logging-operator/pull/143
*** Bug 1694511 has been marked as a duplicate of this bug. ***
Node selector changes or any of the components should cause them to be redeployed.
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