garm/database
Gabriel Adrian Samfira c7d34e0f0e Force transition instances in inconsistent state
If GARM is killed or restarted while creating a runner, there is a chance
that runners remain in creating or deleting state. We've started checking
state transitions in GARM and allow a transition when the new state makes
sense in normal circumstances. However, when recovering from a crash, we
may be in an inconsisten state from which we need to recover.

This change added a ForceUpdateInstance() function that ignores state
transition inconsistencies. For now, we only use it when spinning up a
scale set and check for instance states.

This change also fixes a locking issue.

Signed-off-by: Gabriel Adrian Samfira <gsamfira@cloudbasesolutions.com>
2026-02-11 20:51:32 +02:00
..
common Force transition instances in inconsistent state 2026-02-11 20:51:32 +02:00
sql Force transition instances in inconsistent state 2026-02-11 20:51:32 +02:00
watcher Add agent mode 2026-02-08 00:27:47 +02:00
database.go Rename module 2023-03-12 16:01:49 +02:00