Fedora IoT 43, bootc mode — greenboot-set-rollback-trigger dependency failed?

Ask Fedora
, , ,
1

I have a Raspberry Pi Zero 2 W, and I’ve installed Fedora IoT 43 with the bootc base image.

Everything is working, but I noticed this in the logs:

Oct 27 14:27:05 localhost.localdomain systemd[1]: Dependency failed for greenboot-set-rollback-trigger.service - Greenboot Rollback trigger.
Oct 27 15:14:05 localhost.localdomain systemd[1]: Dependency failed for greenboot-set-rollback-trigger.service - Greenboot Rollback trigger.
Oct 27 16:50:21 localhost.localdomain systemd[1]: Dependency failed for greenboot-set-rollback-trigger.service - Greenboot Rollback trigger.
Oct 27 17:10:20 localhost.localdomain systemd[1]: Dependency failed for greenboot-set-rollback-trigger.service - Greenboot Rollback trigger.
Oct 27 18:19:16 localhost.localdomain systemd[1]: Dependency failed for greenboot-set-rollback-trigger.service - Greenboot Rollback trigger.
Oct 27 18:19:22 localhost.localdomain systemd[1]: Dependency failed for greenboot-set-rollback-trigger.service - Greenboot Rollback trigger.
Oct 27 18:25:05 localhost.localdomain systemd[1]: Dependency failed for greenboot-set-rollback-trigger.service - Greenboot Rollback trigger.
Oct 27 18:36:45 localhost.localdomain systemd[1]: Dependency failed for greenboot-set-rollback-trigger.service - Greenboot Rollback trigger.
Oct 27 19:00:38 localhost.localdomain systemd[1]: Dependency failed for greenboot-set-rollback-trigger.service - Greenboot Rollback trigger.
Oct 27 20:29:05 localhost.localdomain systemd[1]: Dependency failed for greenboot-set-rollback-trigger.service - Greenboot Rollback trigger.

(and more).

What’s going on here? Does this mean that rollbacks won’t work when they’re needed?

2

What’s going on here? Does this mean that rollbacks won’t work when they’re needed?

Short answer: Greenboot will continue to rollback when there is a health-check failure post upgrade.

This is due to greenboot architecture, where reboot and rollback is now decoupled , reboot will occur every time if health check fails(upto 3 times default ). but rollback will only be triggered if reboot attempts are exhausted AND system has been upgraded. This is causing the Dependency failed for greenboot-set-rollback-trigger.service for non upgrade boot ,the condition only satisfies when a system boots post upgraded.

3

Okay, so maybe it should fail once at boot? (Although that doesn’t seem quite right either — warnings shouldn’t indicate “everything is fine”.) Why, though, is it happening over and over again while the system is running?

4

Yes, a failure can create impression of somethings not right. I think the service can be fixed with Resrart=no and ConditionNeedsUpdate= . I can will create an issue issue to track and fix it.

5

Tracking it through: update condition for greenboot-set-rollback-trigger so it only triggers when systems updated · Issue #126 · fedora-iot/greenboot-rs · GitHub

1 Like