Bug 1732936
| Summary: | resources spec don't get updated by the cluster logging operator | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | raffaele spazzoli <rspazzol> | |
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> | |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.1.0 | CC: | aos-bugs, rmeggins | |
| Target Milestone: | --- | |||
| Target Release: | 4.2.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | No Doc Update | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1746542 (view as bug list) | Environment: | ||
| Last Closed: | 2019-10-16 06:31:08 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1746542 | |||
Verified success in 4.2 by: * Created CL instance with request.memory only * Verified Elasticsearch Instance change * Verified Pods change * Modifed CL instance to add limit.memory * Verified Elasticsearch Instance change * Verified Pods change Note: Did find that EO is defaulting values in limits/requests that it should not which is a separate issue but confirmed the EO is reacting to changes unlike what is reported in this BZ The resource changes in deployment. Move to verified 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:2922 |
Description of problem: changing the resource spec in the ClusterLogging CR for the elasticsearch pods does not seem to have any effect if the pods are already running. fragment from the cluster logging object redundancyPolicy: SingleRedundancy resources: limits: cpu: '1' memory: 8Gi requests: cpu: '1' memory: 8Gi fragment from one of the Elastic search deployment: containers: - resources: limits: cpu: '1' memory: 8Gi requests: cpu: '1' memory: 8Gi fragment from the replicaset containers: - resources: limits: cpu: '1' memory: 16Gi requests: cpu: '1' memory: 16Gi and pods also have 16, so in my case they could not be scheduled. Also along the same lines, I changed the node selector in the cluster logging resource and it never got updated the deployment and dependent resources: cluster logging: nodeSelector: node-role.kubernetes.io/es: '' deployment: nodeSelector: machine.openshift.io/cluster-api-machine-role: es node-role.kubernetes.io/es: ''