[zebra.conf] Avoid zebra crash upon empty configuration #2203
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.
- What I did
Current zebra.conf template will generate an invalid configuration file and crash zebra process, when no ipv4 loopback address is defined. Though this will not happen during normal use case, it could cause unexpected zebra crash log when applying 'empty' preset configurations. This change intends to fix this problem.
- How I did it
Add check in zebra.conf template similar to what we are doing for ipv6 loopback addresses