Bug 1323517 - Discrepancy between snapper config and cron schedule
Summary: Discrepancy between snapper config and cron schedule
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: snapper
Version: 7.2
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Ondrej Kozina
QA Contact: Lin Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-03 20:45 UTC by prasun.gera
Modified: 2021-09-03 13:03 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-16 13:38:32 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description prasun.gera 2016-04-03 20:45:04 UTC
Description of problem:

The snapper hourly cronjob just creates snapshots whereas the daily one is responsible for cleanup. This makes the TIMELINE_LIMIT_HOURLY parameter in the snapper config useless since all the hourly snapshots will be kept around until the daily job is called for cleanup. In steady state, you will have ~24 snapshots irrespective of the config. 

/etc/cron.hourly/snapper:

if [ "$TIMELINE_CREATE" = "yes" ] ; then
        snapper --config=$CONFIG --quiet create --description="timeline" --cleanup-algorithm="timeline"
    fi


/etc/cron.daily/snapper:

if [ "$TIMELINE_CLEANUP" = "yes" ] ; then
        snapper --config=$CONFIG --quiet cleanup timeline
    fi



Version-Release number of selected component (if applicable):


How reproducible:
Easy

Steps to Reproduce:
1. Set TIMELINE_LIMIT_HOURLY in /etc/snapper/configs/config_name
2.
3.

Actual results:

More snapshots than specified

Expected results:

Same number of snapshots as specified

Additional info:

Comment 3 Jakub Krysl 2019-10-02 11:45:09 UTC
Mass migration to lilin.


Note You need to log in before you can comment on or make changes to this bug.