Bug 1686173
| Summary: | cluster logging operator incorrectly sets memory and cpu limits after changes from defaults | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jeff Cantrill <jcantril> |
| Component: | Logging | Assignee: | ewolinet |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.1.0 | CC: | anli, aos-bugs, ewolinet, rmeggins |
| Target Milestone: | --- | ||
| Target Release: | 4.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-04 10:45:04 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: | |||
The resource are changed in the CRD elasticsearch. But the elasticsearch pod wasn't restarted. Is it possible you ran into https://bugzilla.redhat.com/show_bug.cgi?id=1694522? 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 |
Description of problem: Version-Release number of selected component (if applicable): 4.0 How reproducible: Always Steps to Reproduce: 1. Deploy ClusterLogging without defining resources. CLO defaults request and limit values 2. Edit ClusterLogging instance to spec resources.request.memory only Actual results: Component roles out with resources.{request, limit}.memory Expected results: Component roles out with only the resources spec'd in ClusterLogging Additional info: I have not tested but I assume the issue is relevant to each logging component