Recently we had a discussion about an automatic handling of updates ("dnf-automatic") in Fedora Server: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/HUKUMMCLBYN2TCR36GXUNLOPVHF5QV5G/
More details about dnf-automatic at: https://lists.centos.org/pipermail/centos-devel/2021-September/077329.html
And there exists a RFE in bugzille for centos: https://bugzilla.redhat.com/show_bug.cgi?id=2004572
We should decide whether to take up the RFE and include automatic notification in Fedora Server, either as part of the default installation or as an installation option. And we have to decide about the default configuration (basically just notification or notification and automatic installation in one go)
I would propose: Notify of available updates on every login. Automatically update (critical) security updates. Do not automatically update (major) versions of products liable to cause havoc.
Most server systems have quite infrequent logins, so above would be acceptable midway.
Issue tagged with: pending activity
Metadata Update from @pboy: - Issue tagged with: meeting
Issue tagged with: in progress
i like the idea of seeing what updates are needed on login. Since this is a server I wouldn't automatically install any updates. A service might need to be restarted after the updates.
We sort of already have this, since we install Cockpit's package management tool by default, which will always show pending updates.
It's really not common to log directly into a server unless something is going wrong. A better solution for managing updates would be to use something like Red Hat Satellite, but I'm not sure if that has full support for Fedora Server. It's worth looking into.
Metadata Update from @pboy: - Issue untagged with: meeting
Log in to comment on this ticket.