Bug 1651002

Summary: systemd presets request: sa-update.timer
Product: [Fedora] Fedora Reporter: Kevin Fenzi <kevin>
Component: fedora-releaseAssignee: Mohan Boddu <mboddu>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 31CC: bcotton, dennis, jdisnard, jkeating, kellin, kevin, mboddu, pbrobinson, sgallagh, zbyszek
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: fedora-release-31-4 fedora-release-32-2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-30 03:43:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kevin Fenzi 2018-11-18 16:57:38 UTC
* Does the service require post-rpm-installation configuration in order to be useful (for example, does it need manual edits to a configuration file)?

Nope

* Does the service listen on a network socket for connections originating on a separate physical or virtual machine?

Nope

* Is the service non-persistent (i.e. run once at startup and exit)?

Runs once each timer run.

* What is the exact name (or names) of the systemd unit files to be enabled?

sa-update.timer

* Is this request for all Fedora deliverables or only for some Editions (list them)?

All. 

See https://bugzilla.redhat.com/show_bug.cgi?id=1645826

The idea is that if you have spamassassin installed, you want the data files to be updated for other tools that call spamassassin.

Comment 1 Ben Cotton 2019-08-13 17:06:16 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 2 Ben Cotton 2019-08-13 19:41:05 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 3 Kevin Fenzi 2020-04-20 00:08:02 UTC
Sgallagh: Can you look at this please? Or any other co-maintainers. ;)

Comment 4 Stephen Gallagher 2020-04-20 13:00:16 UTC
Wow, this one really slipped through the cracks. Sorry about that.

Merged to Rawhide. Do you need this backported to F32? If so, it'll need a Freeze Exception at this point.

Comment 5 Kevin Fenzi 2020-04-22 16:34:39 UTC
I think rawhide is fine. It's waited this long... Thanks!

Comment 6 Kevin Fenzi 2020-04-25 18:08:04 UTC
So the user who requested this would like to have it also in stable releases. 

Can you also do stable releases here?

Comment 7 Fedora Update System 2020-04-28 12:53:50 UTC
FEDORA-2020-61a861a2d9 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-61a861a2d9

Comment 8 Fedora Update System 2020-04-28 12:53:51 UTC
FEDORA-2020-938393aa3c has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-938393aa3c

Comment 9 Fedora Update System 2020-04-29 01:55:44 UTC
FEDORA-2020-938393aa3c has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-938393aa3c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-938393aa3c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2020-04-29 02:04:59 UTC
FEDORA-2020-61a861a2d9 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-61a861a2d9`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-61a861a2d9

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Ben Cotton 2020-04-29 23:53:26 UTC
So according to git, the `enable sa-update.timer` line was added a couple of months before this bug was opened:
https://src.fedoraproject.org/rpms/fedora-release/c/12e91163a3c7054e1ebf4a725dc2b2fbe4fefd41

On my F31 system, with FEDORA-2020-938393aa3c installed, I see it twice:
[root@normal ~]# grep -B 2 sa-update /usr/lib/systemd/system-preset/90-default.preset

# https://bugzilla.redhat.com/show_bug.cgi?id=1218999
enable sa-update.timer
--
# Enable regular update of SpamAssassin data files
# https://bugzilla.redhat.com/show_bug.cgi?id=1651002
enable sa-update.timer
[root@normal ~]# 

Am I missing something or is this update not going to fix the issue?

Comment 12 Fedora Update System 2020-04-30 03:43:18 UTC
FEDORA-2020-938393aa3c has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2020-05-01 00:36:33 UTC
FEDORA-2020-61a861a2d9 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.