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
Pass on release:4.0.0-0.nightly-2019-02-15-034921
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.