[Multi-Asic] Fix for multi-asic where we should allow namespace docker local communication on its docker/eth0 ip #5364
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.
Why/What i did:
Fix for multi-asic where we should allow namespace docker local communication on its docker/eth0 ip
. Without this TCP Connection to Redis Server running on docker eth0 ip does not happen in namespace if there is Catch all DROP Rule.
Found this issue as part of debugging
a) lldpmgrd was not able to start in namespace (uses Redis TCP Connection)
b) Feature auto restart not working for namespace docker (supervisor-proc-exit-listener also uses Redis TCP Connection)
How I verify:
After fix both issue (a) and (b) are working fine.