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 1694511 - Redeployed cluster logging when nodeSelector changed in CLO
Summary: Redeployed cluster logging when nodeSelector changed in CLO
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-04-01 01:22 UTC by Anping Li
Modified: 2019-04-09 05:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2019-04-01 13:03:56 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Anping Li 2019-04-01 01:22:39 UTC
Description of problem:
The pod should be redeployed once the nodeSelector is changed in CLO CR. That is the following of a

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 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:

Comment 1 Jeff Cantrill 2019-04-01 13:03:56 UTC
Closing in favor of as work is required in both operators to support the fix

*** This bug has been marked as a duplicate of bug 1694097 ***

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