[16.0] Edge apps are not activated after rolling back from a snapshot#5408
Conversation
For every user action that starts a STOPPED application or creates a new one, the system first calls doActivate and then doUpdate. doActivate is responsible for marking an application as high-priority. During doUpdate, the system checks this priority flag: - If the app is high-priority, it starts immediately. - If not, it will only start after all higher-priority applications have started or when the startup timeout is reached. In the snapshot-rollback flow, the application is started automatically through reactToSnapshotRollback instead of going through doActivate. Because of this, the app never receives a priority assignment. This PR ensures that priority is also set during reactToSnapshotRollback. Signed-off-by: Ioannis Sfakianakis <[email protected]> (cherry picked from commit c5c3d2f)
|
@jsfakian you've marked in the check list that the PR's title is correct, but it's not... please, fix according the backport template.... |
|
Since the go tests workflow runs out of disk space it would be good to verify with 'make test(s)' that the tests pass. |
|
@jsfakian , could you please run locally and post the logs here? That's how we are doing when go-tests are running out of disk space. This is fixed on master, but it requires the backport of some PRs, which is not available on 16.0 and other stable branches. |
I get a timeout when I run |
|
I can run the tests one by one:
|
The tests pass locally, so we can merge. |
Description
Backport of #5403
PR dependencies
None.
How to test and validate this PR
Changelog notes
Checklist
check them.