In certain basic situations (eg. --tags=update when there are no new patches to install), a change is noted against the domain tier but not the engine tier -- this ultimately results in a partial restart of the server, as the domain tier's handlers are executed but not the engine tier's...
Either ensure all tiers restart (in correct order), or avoid domain tier having a change marked against it when nothing has actually changed.
Looks like the culprit is tasks/update-jdk.yml -- not correctly identifying when the shutdown / startup needs to actually run (complex when condition)...
In certain basic situations (eg.
--tags=update
when there are no new patches to install), a change is noted against the domain tier but not the engine tier -- this ultimately results in a partial restart of the server, as the domain tier's handlers are executed but not the engine tier's...Either ensure all tiers restart (in correct order), or avoid domain tier having a change marked against it when nothing has actually changed.