Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1694097 - Redeployed cluster logging when nodeSelector changed for components
Summary: Redeployed cluster logging when nodeSelector changed for components
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.1.0
Assignee: ewolinet
QA Contact: Anping Li
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-29 14:07 UTC by Anping Li
Modified: 2019-04-09 05:10 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Github openshift cluster-logging-operator pull 143 None None None 2019-04-01 13:05:25 UTC
Github openshift elasticsearch-operator pull 114 None None None 2019-04-01 13:05:25 UTC

Description Anping Li 2019-03-29 14:07:03 UTC
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):

How reproducible:

Steps to Reproduce:
1. Deploy cluster logging via cluster-logging-operator
2. Provide instance CR 
  oc create -f 
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:

Comment 1 Rich Megginson 2019-03-29 14:12:24 UTC
right - you have to set the clusterlogging managementState to Unmanaged

Comment 5 Jeff Cantrill 2019-04-01 13:03:56 UTC
*** Bug 1694511 has been marked as a duplicate of this bug. ***

Comment 6 Jeff Cantrill 2019-04-01 13:05:26 UTC
Node selector changes or any of the components should cause them to be redeployed.

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