garm/workers/scaleset
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
..
controller.go Some slight cleanup 2025-08-31 21:58:42 +00:00
controller_watcher.go Ensure scale set exists 2025-08-23 18:55:08 +00:00
interfaces.go Add copyright header 2025-05-20 09:43:29 +00:00
scaleset.go Force transition instances in inconsistent state 2026-02-11 20:51:32 +02:00
scaleset_helper.go Handle new jobID for scale sets 2025-07-18 08:20:50 +00:00
scaleset_listener.go Scale sets stability fixes 2025-08-28 11:53:40 +00:00
util.go Add copyright header 2025-05-20 09:43:29 +00:00