Comment 2 for bug 1936976

Reviewed: https://review.opendev.org/c/starlingx/metal/+/801545
Committed: https://opendev.org/starlingx/metal/commit/74bfeba7d38dddf5820b2e341f5d3c5e49282a9e
Submitter: "Zuul (22348)"
Branch: master

commit 74bfeba7d38dddf5820b2e341f5d3c5e49282a9e
Author: Eric MacDonald <email address hidden>
Date: Tue Jul 20 18:54:14 2021 -0400

    Increase maximum preserved crash dump vmcore file size to 5Gi

    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 <email address hidden>