Backup and Restore: Coredump.conf not being restored

Bug #1978611 reported by Hugo Nicodemos Brito
6
This bug affects 1 person
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-parameter-add platform coredump process_size_max=2.1G
system service-parameter-add platform coredump external_size_max=2.2G
system service-parameter-add platform coredump max_use=200M
system service-parameter-add platform coredump keep_free=1.1G
2) run the B&R

3) Check the service parameters table and the file /etc/systemd/coredump.conf.d/coredump.conf after restore.

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-parameter-update platform coredump <parameter>=<value>

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ansible-playbooks (master)
Changed in starlingx:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ansible-playbooks (master)

Reviewed: https://review.opendev.org/c/starlingx/ansible-playbooks/+/845762
Committed: https://opendev.org/starlingx/ansible-playbooks/commit/1ed375a0446bfc39efe2e88ecf3e422e486003ff
Submitter: "Zuul (22348)"
Branch: master

commit 1ed375a0446bfc39efe2e88ecf3e422e486003ff
Author: Hugo Brito <email address hidden>
Date: Tue Jun 14 11:11:13 2022 -0300

    B&R: Restore coredump.conf.d directory

    The coredump.conf system file was not restored with the configurations
    that were done through the service parameters table before the backup.
    This overrides all the content of coredump configuration directory
    during the restore process.

    Test Plan:
    - Modify coredump service parameter prior to taking platform backup:
    system service-parameter-add platform coredump <parameter>=<value>
    - Verify that coredump.conf file is updated accordingly.
    - Perform platform backup and restore.
    - Verify that both coredump service parameter and coredump.conf file
    were restored with the last configured value.
    PASS: B&R playbooks ran without errors (AIO-SX and AIO-DX).

    Closes-bug: 1978611

    Signed-off-by: Hugo Brito <email address hidden>
    Change-Id: I2d268b92beaccc31e595ab3b36e7414fc45abcbc

Changed in starlingx:
status: In Progress → Fix Released
Ghada Khalil (gkhalil)
tags: added: stx.7.0 stx.update
Changed in starlingx:
importance: Undecided → Medium
assignee: nobody → Hugo Nicodemos Brito (hbrito)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.