RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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
}

Not really sure if this is related: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573178

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.