diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2017-10-27 15:11:38 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-10-27 15:11:38 -0700 |
| commit | 2c81304511afcf03b35583f85040fb7d0b83cad5 (patch) | |
| tree | 3c496a4e621fa6545385e4c9c9a3a70f3883c70c /inventory/byo/hosts.byo.glusterfs.registry-only.example | |
| parent | d40744574297204f5e7c326491ae1af07fab17ed (diff) | |
| parent | 205d03455cf37d66f3629de7951463d755b72b16 (diff) | |
| download | openshift-2c81304511afcf03b35583f85040fb7d0b83cad5.tar.gz openshift-2c81304511afcf03b35583f85040fb7d0b83cad5.tar.bz2 openshift-2c81304511afcf03b35583f85040fb7d0b83cad5.tar.xz openshift-2c81304511afcf03b35583f85040fb7d0b83cad5.zip | |
Merge pull request #5897 from jcantrill/1506073_cpu_request_match_limit
Automatic merge from submit-queue.
bug 1506073. Lower cpu request for logging when it exceeds limit
This PR fixes https://bugzilla.redhat.com/show_bug.cgi?id=1506073 by:
* Lowering the CPU request to match the limit when the request is greater then a specified limit
I have an open question on if this is an acceptable change of if it makes the outcome unexpected. Should we prefer to exit during the deployment and advise the operator to correct their inventory?
Diffstat (limited to 'inventory/byo/hosts.byo.glusterfs.registry-only.example')
0 files changed, 0 insertions, 0 deletions