Latest revision as of 14:42, 12 September 2023

Enable fwupd-refresh.timer by default on IoT, CoreOS & Server editions

Summary

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.

On desktops, firmware updates are generally coordinated by graphical applications such as GNOME Software or Plasma Discover so we will not enable it on those editions.

Owner

Name: Timothée Ravier, Renata Ravanelli
Email: travier@redhat.com, rravanel@redhat.com

Current status

Targeted release: Fedora Linux 39
Last updated: 2023-09-12
devel thread
FESCo issue: https://pagure.io/fesco/issue/3054
Tracker bug: #2233233
Release notes tracker: #1002

Detailed Description

Firmware for hardware devices can have bugs and firmware updates generally help address those. Firmware updates might however need manual interaction, a reboot or device unplug/re-plug so we can not enable firmware update by default.

This change thus only enable notifying about new firmware updates, not installing them.

With this change, Fedora installations will contact the Linux Vendor Firmware Service CDN (LVFS, https://cdn.fwupd.org/) to get the updated metadata but will not send any information about the hardware without user interaction.

See the LVFS privacy policy at https://lvfs.readthedocs.io/en/latest/privacy.html.

Link to the unit being enabled: https://github.com/fwupd/fwupd/tree/main/data/motd

Feedback

Discussion for each impacted edition:

CoreOS: https://github.com/coreos/fedora-coreos-tracker/issues/1512 (Accepted)
IoT: https://pagure.io/fedora-iot/issue/52 (Accepted)
Server: https://pagure.io/fedora-server/issue/115 (Accepted)

Benefit to Fedora

Knowing when firmware updates can be applied on a system would make systems more reliable.

Scope

Proposal owners: Do the change required to enable fwupd-refresh.timer by default

Other developers: N/A

Release engineering: N/A #Releng issue number

Policies and guidelines: N/A (not needed for this Change)

Trademark approval: N/A (not needed for this Change)

Alignment with Community Initiatives: N/A

Upgrade/compatibility impact

No impact, it is just a refresh to check about new firmware updates. It will be enabled for existing and new systems.

How To Test

Install a system on hardware that has an old firmware and check if you get a notification about a new firmware update on login in the MOTD.

User Experience

User will still have to manually update their firmware.

Dependencies

There are no dependencies

Contingency Plan

Contingency mechanism: Continue to ship things the way we ship them today
Contingency deadline: N/A
Blocks release? N/A

Documentation

N/A (not a System Wide Change)

Release Notes

@@ Line 1: / Line 1: @@
-{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
-{{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ documentation].}}
-{{admon/tip | Report issues | To report an issue with this template, file an issue in the [https://pagure.io/fedora-pgm/pgm_docs pgm_docs repo].}}
-<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
 = Enable fwupd-refresh.timer by default on IoT, CoreOS & Server editions =
-{{Change_Proposal_Banner}}
 == Summary ==
@@ Line 24: / Line 15: @@
 == Current status ==
-[[Category:ChangePageIncomplete]]
+[[Category:ChangeAcceptedF39]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
@@ Line 42: / Line 33: @@
 ON_QA -> change is fully code complete
 -->
-* [<will be assigned by the Wrangler> devel thread]
+* [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/TSJRZVSCM4W66UJ57RJPMGXVEDHMIOWK/ devel thread]
-* FESCo issue: <will be assigned by the Wrangler>
+* FESCo issue: https://pagure.io/fesco/issue/3054
-* Tracker bug: <will be assigned by the Wrangler>
+* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2233233 #2233233]
-* Release notes tracker: <will be assigned by the Wrangler>
+* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/1002 #1002]
 == Detailed Description ==
 Firmware for hardware devices can have bugs and firmware updates generally help address those. Firmware updates might however need manual interaction, a reboot or device unplug/re-plug so we can not enable firmware update by default.
@@ Line 58: / Line 48: @@
 See the LVFS privacy policy at https://lvfs.readthedocs.io/en/latest/privacy.html.
+Link to the unit being enabled: https://github.com/fwupd/fwupd/tree/main/data/motd
 == Feedback ==
 <!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->
-None so far.
+Discussion for each impacted edition:
+* CoreOS: https://github.com/coreos/fedora-coreos-tracker/issues/1512 (Accepted)
+* IoT: https://pagure.io/fedora-iot/issue/52 (Accepted)
+* Server: https://pagure.io/fedora-server/issue/115 (Accepted)
 == Benefit to Fedora ==

Search

Changes/EnableFwupdRefreshByDefault: Difference between revisions