Some users are running processes in the devices that can't be interrupted when the HUP process is initiated from the dashboard. HUP's current implementation doesn't take into account the containers' locks, so the HUP process will just run when invoked, killing any running process.
This interruption has resulted in some users complaining that they would have to manually control HUP when they consider it should be done by balena.

Expected Behavior

startOsUpdate should not update if a user lock exists

Actual Behavior

startOsUpdate doesn't take into account user service locks, causing some interrupted processes.

Steps to Reproduce the Problem

1. Have a user service lock
2. call startOsUpdate
3. os will be updated even if user service lock existed

Specifications

• SDK version:
• Browser:
• Node version:
• Npm version:
• OS:

References