Make services' activity status saving more consistent #6066
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context:
Very often, when the node is restarted, the activity of services is deactivated in an arbitrary manner.
The reason is onordered and concurrent run of updateActiveServicesInUserConfig method on start of each service.
This patch orders run of updateActiveServicesInUserConfig, so that active-services property with all active servies will be written the last.
Fixes: #6055