Default Coredump Configuration mismatch between Documentation and actual config

[Heron Vieira]

Brief Description
-----------------
According to the document (https://docs.starlingx.io/system_configuration/kubernetes/change-the-default-coredump-configuration-51ff4ce0c9ae.html), the parameter “ProcessSizeMax” and “ExternalSizeMax” are set to 2G by default. But, it seems that the default value described in the document is not applied.
According to Support investigation

the default values are commented out by default in core dump configuration file “coredump.conf” as below.

[sysadmin@controller-0 ~(keystone_admin)]$ cat /etc/systemd/coredump.conf.d/coredump.conf

[Coredump]
..
#ProcessSizeMax=2G
#ExternalSizeMax=2G

So it looks that some other default system value has been applied.
I also noticed that when

“system service-parameter-add platform coredump <parameter>=<value>”.

command is used, coredump.conf indeed contains the new value.

Severity
--------
Minor

Expected Behavior
------------------
Coredump configuration default values should be applied on install

Actual Behavior
----------------
Coredump configuration default values is not being applied on install

Reproducibility
---------------
Reproducible

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/starlingx/stx-puppet/+/897856
Committed: https://opendev.org/starlingx/stx-puppet/commit/2a58155df64224ef3298b419270c7080c289ce16
Submitter: "Zuul (22348)"
Branch: master

commit 2a58155df64224ef3298b419270c7080c289ce16
Author: Heron Vieira <email address hidden>
Date: Tue Oct 10 13:29:52 2023 -0300

    Add coredump runtime manifest to config

    Add the coredump runtime manifest to the config puppet manifest to
    update the coredump configuration with default parameters upon
    bootstrap.

    Test plan
    PASS: AIO-SX install, bootstrap and initial unlock
    PASS: Verify if coredump config file is changed before initial unlock,
          after bootstrap.
    PASS: Verify if coredump config file is changed after initial unlock.

    Closes-bug: 2039064

    Change-Id: I3235afde70f6def71b22e11bd3b61ec9f5cca908
    Signed-off-by: Heron Vieira <email address hidden>

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/starlingx/config/+/897795
Committed: https://opendev.org/starlingx/config/commit/50a658cedd0a99dec7b97b3176d84e43eb77c340
Submitter: "Zuul (22348)"
Branch: master

commit 50a658cedd0a99dec7b97b3176d84e43eb77c340
Author: Heron Vieira <email address hidden>
Date: Tue Oct 10 09:02:45 2023 -0300

    Add coredump default service parameters

    Adding coredump process_size_max, external_size_max and
    keep_free default service parameters so coredump service is configured
    with default values from the start, keeping it explicit for the user
    what is configured on a fresh install.

    Test plan
    PASS: AIO-SX install, bootstrap and initial unlock
    PASS: Verify if coredump service parameters are added after initial
          unlock.
    PASS: Verify if coredump config file is changed after initial unlock

    Depends-On: https://review.opendev.org/c/starlingx/stx-puppet/+/897856

    Closes-bug: 2039064

    Change-Id: I13b1c1e0d6c34b34cf6ed3f1cb86c8511ac24b44
    Signed-off-by: Heron Vieira <email address hidden>