Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2233233 - Enable fwupd-refresh.timer by default on IoT, CoreOS & Server editions
Summary: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server editions
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Timothée Ravier
QA Contact:
URL:
Whiteboard:
Depends On: 2236496 2236498
Blocks: F39Changes
TreeView+ depends on / blocked
 
Reported: 2023-08-21 18:47 UTC by Adam Williamson
Modified: 2024-04-26 01:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-14 18:57:27 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Adam Williamson 2023-08-21 18:47:25 UTC 
This is a tracking bug for Change: Enable fwupd-refresh.timer by default on IoT, CoreOS & Server editions
For more details, see: https://fedoraproject.org/wiki/Changes/EnableFwupdRefreshByDefault

fwupd-refresh systemd service unit & timer are designed to regularly refresh the fwupd metadata and update the MOTD when new firmware updates can be applied on a system. We want to enable the fwupd-refresh.timer by default on IoT, CoreOS & Server editions so that users get reminded about firmware updates.

If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.
Comment 1 Adam Williamson 2023-08-22 21:18:48 UTC 
I don't think this is done. AFAICS, the preset is still specifically set to disable the timer and the service in current Rawhide fwupd package.

The timeline here is kinda awkward. The 'testable' deadline was 2023-08-08, and the 'code complete' deadline was 2023-08-21. But FESCo didn't accept this Change until 2023-08-17, nine days *after* the Change should have been 'testable' and only four days before it should be 'code complete'. I'm not sure that approving Changes this late was a great idea.

I'm currently going through all F39 Changes checking on their status, and will ask FESCo to look at this one and similar late-accepted ones and decide what they want to do with them.
Comment 2 Timothée Ravier 2023-08-23 13:17:51 UTC 
Agree that it's not late this was approved so late. The FESCo issue creation was delayed due to the missing FGM.

Moving to POST, and I'll file an exception for the beta freeze.

PRs:
- https://src.fedoraproject.org/rpms/fedora-release/pull-request/279
- https://github.com/coreos/fedora-coreos-config/pull/2562
Comment 3 Timothée Ravier 2023-10-02 09:52:52 UTC 
With https://bugzilla.redhat.com/show_bug.cgi?id=2236498 completed, we should be 100% complete for this one now.
Comment 4 Aoife Moloney 2023-11-14 18:57:27 UTC 
F39 was released on November 7th, so I am closing this tracker. If this Change was not completed, please notify me ASAP.
Comment 5 Maryann Manning 2024-04-19 07:57:40 UTC Comment hidden (spam)
Note You need to log in before you can comment on or make changes to this bug.