Bug 1675381

Summary: Cluster Logging does not set cpu and memory defaults when nothing is defined for the clusterlogging object
Product: OpenShift Container Platform Reporter: Jeff Cantrill <jcantril>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: high Docs Contact:
Priority: urgent    
Version: 4.1.0CC: aos-bugs, rmeggins
Target Milestone: ---   
Target Release: 4.1.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-04 10:44:00 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:

Description Jeff Cantrill 2019-02-11 20:52:17 UTC
The ClusterLogging stack does not define component cpu and memory defaults if these values are not defined for the ClusterLogging object.  The CLO should mint deployments to use the same defaults (e.g. 16G for ES min/max) used by openshift-ansible in 3.11

Comment 1 Anping Li 2019-02-15 06:23:09 UTC
Pass on release:4.0.0-0.nightly-2019-02-15-034921

Comment 4 errata-xmlrpc 2019-06-04 10:44:00 UTC
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.