Open AdmiralNemo opened 2 hours ago
Do you have substantial data in /etc
?
Do you have substantial data in
/etc
?
Not really?
[core@k8s-aarch64-n0 ~]$ sudo du -xhs /etc
41M /etc
Most of that appears to come from /etc/selinux
and /etc/udev
. The only data I have added there is 27K in /etc/kubernetes
Describe the bug
On certain slow systems, such as Raspberry Pis, the ostree-finalize-staged.service unit fails often because it takes "too long" to do its work. This often results in reboot loops, where Zincati continuously tries to apply the update, but this fails, so the machine reboots back into the old version.
Reproduction steps
This is consistently reproducible for me on my "regular" Raspberry Pi 4b devices, with "generic" class 10 SD cards. I do not notice it on my CM4 devices that use eMMC.
Expected behavior
I would expect updates to succeed, regardless of how long they take.
Actual behavior
Especially when an upgrade requires "pruning" a previous version of FCOS, updates fail to apply and machines get stuck in a reboot loop. Manually running
rpm-ostree cleanup -r
usually resolves it.Increasing the timeout with a unit drop-in configuration file also resolves the issue, e.g.
System details
metal
: Raspberry Pi 4bButane or Ignition config
No response
Additional information
The
ostree-finalized-staged.service
unit file has this snip:I guess 5 minutes is probably not "quite long" enough?