Default Coredump Configuration mismatch between Documentation and actual config
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Heron Vieira |
Bug Description
Brief Description
-----------------
According to the document (https:/
According to Support investigation
the default values are commented out by default in core dump configuration file “coredump.conf” as below.
[sysadmin@
[Coredump]
..
#ProcessSizeMax=2G
#ExternalSizeMax=2G
So it looks that some other default system value has been applied.
I also noticed that when
“system service-
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
Changed in starlingx: | |
status: | New → In Progress |
Changed in starlingx: | |
importance: | Undecided → Low |
assignee: | nobody → Heron Vieira (hevieira) |
tags: | added: stx.9.0 stx.config |
Reviewed: https:/ /review. opendev. org/c/starlingx /stx-puppet/ +/897856 /opendev. org/starlingx/ stx-puppet/ commit/ 2a58155df64224e f3298b419270c70 80c289ce16
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 2a58155df64224e f3298b419270c70 80c289ce16
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: I3235afde70f6de f71b22e11bd3b61 ec9f5cca908
Signed-off-by: Heron Vieira <email address hidden>