Backup and Restore: Coredump.conf not being restored
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Hugo Nicodemos Brito |
Bug Description
Brief Description
-----------------
The coredump.conf system file was not restored with the configurations that were done through the service parameters table before the backup. So, the coredump.conf and the table don't match after B&R process.
Severity
--------
<Minor: System/Feature is usable with minor issue>
Steps to Reproduce
------------------
1) Configure coredump parameters through service parameter table before backup:
system service-
system service-
system service-
system service-
2) run the B&R
3) Check the service parameters table and the file /etc/systemd/
Expected Behavior
------------------
The coredump.conf file configured before backup must be equal to the coredump.conf file after restore. Also, the coredump.conf file must match with the coredump parameters configured in the service parameters table. Otherwise, the coredump.conf must have the default values.
Actual Behavior
----------------
coredump.conf file configured before backup doesn't match with coredump.conf file after restore.
Reproducibility
---------------
100% Reproducible
System Configuration
-------
<One node system, Two node system, Multi-node system, Dedicated storage, https, IPv4, IPv6 etc.>
Branch/Pull Time/Commit
-------
Master
Workaround
----------
Update the service parameters table after restore:
system service-
tags: | added: stx.7.0 stx.update |
Changed in starlingx: | |
importance: | Undecided → Medium |
assignee: | nobody → Hugo Nicodemos Brito (hbrito) |
Fix proposed to branch: master /review. opendev. org/c/starlingx /ansible- playbooks/ +/845762
Review: https:/