check: send systemd READY even with no runnable config #2662
+4
−0
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.
When keepalived starts without any VRRP/LVS/BFD blocks, it does not spawn any child processes. In this case, systemd never receives a READY=1 notification, and the service eventually times out during startup.
Fix this by explicitly calling systemd_notify_running() when there are no children, so that systemd always gets a readiness signal, even with an empty configuration.