StarlingX Bare Metal and Node Management, Hardware Maintenance
74bfeba7d3
The current crashDumpMgr service has several filesystem protection methods that can result in the auto deletion of a crashdump vmcore file. One is a hard cap of 3Gi. This max vmcore size is too small for some applications. Crash dump vmcore files can get big with servers that have a lot of memory and big apps. This update modifies the crashDumpMgr service file max_size override to 5Gi. Test Plan: PASS: Verify change functions as expected PASS: Verify change is inserted after patch apply PASS: Verify crash dump under-size threshold handling PASS: Verify crash dump over-size threshold handling PASS: Verify change is reverted after patch removal Change-Id: I867600460ba9311818ace466986603f5bffe4cd7 Closes-Bug: 1936976 Signed-off-by: Eric MacDonald <eric.macdonald@windriver.com> |
||
---|---|---|
api-ref/source | ||
bsp-files | ||
devstack | ||
doc | ||
installer | ||
kickstart | ||
mtce | ||
mtce-common | ||
mtce-compute | ||
mtce-control | ||
mtce-storage | ||
releasenotes | ||
tools/rvmc/centos | ||
.gitignore | ||
.gitreview | ||
.zuul.yaml | ||
centos_build_layer.cfg | ||
centos_iso_image.inc | ||
centos_pkg_dirs | ||
centos_stable_docker_images.inc | ||
CONTRIBUTORS.wrs | ||
LICENSE | ||
pylint.rc | ||
README.rst | ||
test-requirements.txt | ||
tox.ini |
metal
StarlingX Bare Metal Management