Bug 1031715 - bacula bconsole pruning messages - wrong date calculation
Summary: bacula bconsole pruning messages - wrong date calculation
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: bacula
Version: 6.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Josef Ridky
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-18 15:24 UTC by Nelson Marques
Modified: 2016-07-22 08:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-22 08:40:26 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Nelson Marques 2013-11-18 15:24:29 UTC
Description of problem: I am getting a few messages from bacula like:

18-Nov 05:06 bacula.ops.impresa.pt JobId 1080: Begin pruning Jobs older than 43 years 5 months 2 days 5 hours 6 mins 13 secs.
18-Nov 05:06 bacula.ops.impresa.pt JobId 1080: No Jobs found to prune.
18-Nov 05:06 bacula.ops.impresa.pt JobId 1080: Begin pruning Jobs.
18-Nov 05:06 bacula.ops.impresa.pt JobId 1080: No Files found to prune.
18-Nov 05:06 bacula.ops.impresa.pt JobId 1080: End auto prune.

While searching on the internet I got this link which suggests this might have been fixed in 5.0.1. If this verifies is it possible to consider na update to 5.0.1 or backport fix? I'm available to help testing.


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

How reproducible: Always

Steps to Reproduce: Run bconsole/bat and check console output; Same on jobs.

Actual results: Values are not right and no recycle/pruning

Expected results: Values should be realistic and recycle/pruning working

Additional info:

Pool
{
    Name = ENV_QA
    Pool Type = Backup
    Recycle = yes
    AutoPrune = yes
    Volume Retention = 8 days
    LabelFormat = "ENV_QA_"
    Maximum Volumes = 9
    RecyclePool = ENV_QA
}

Comment 2 Nelson Marques 2013-11-18 15:53:44 UTC
Not really sure if this is related: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573178

Comment 3 Josef Ridky 2016-07-22 08:40:26 UTC
Red Hat Enterprise Linux version 6 is entering the Production 2 phase of its lifetime and this bug doesn't meet the criteria for it, i.e. only high severity issues will be fixed. Please see https://access.redhat.com/support/policy/updates/errata/ for further information.

This issue is fixed in Red Hat Enterprise Linux version 7.


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