How to schedule and monitor auto-updates?

I successfully upgraded from Fedora CoreOS to uCore without problems.
The steps described here worked well: GitHub - ublue-os/ucore: An OCI base image of Fedora CoreOS with batteries included

But before this I used Metrics | Zincati to keep control of my system to check if the updates were installed.
And I had a schedule with Zincati to do the upgrade (if applicable) during night.

In the documentation of uCore-minimum (GitHub - ublue-os/ucore: An OCI base image of Fedora CoreOS with batteries included) is stated that Zincati is disabled.

  • Disables Zincati auto upgrade/reboot service

That is indeed the case, the metrics exporter service I had running stopped working as well as the Zincati socket was not available anymore.

How are auto-updates now scheduled? Can I change that schedule? And can I monitor the updates?

3 Likes

Did you find an answer on how to have automatic updates?

The uCore readme talks about uCore-minimal having automatic staging:

  • Enables staging of automatic system updates via rpm-ostreed

And I see this happening on my installation of uCore…. but I haven’t yet seen it automatically reboot to enact those staged updates.

I think the key portion of what you found is in the phrasing, automatic staging of updates, which means, they are ready to install as soon as you reboot.

You can check if automatic updating is happening by looking at the service logs of the uupd service (journalctl -u uupd.service), and you can see if there is a staged update waiting by running the command rpm-ostree status. But it seems as though you’ll still need to manually reboot every so often to apply those staged updates.