Fix PANIC in route-agent pod during gw migration #332
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
During gateway node migration, on some occasions it was observed that there was an error while adding an FDB entry which results in PANIC and route-agent pod gets restarted. The reason why FDB entry failed is because of trying to configure an FDB entry with empty ipAddress. This patch fixes this issue by ensuring that we wait until a POD gets an IPAddress and process it only after one is assigned to it. Signed-off-by: Sridhar Gaddam <sgaddam@redhat.com>
|
🤖 Created branch: z_pr332/sridhargaddam/fix-route-agent-issue |
mangelajo
approved these changes
Feb 7, 2020
tpantelis
approved these changes
Feb 7, 2020
|
🤖 Closed branches: [z_pr332/sridhargaddam/fix-route-agent-issue] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
During gateway node migration, on some occasions, it was observed
that there was an error while adding an FDB entry which results
in PANIC and route-agent pod gets restarted. The reason why FDB
entry failed is because of trying to configure an FDB entry with
empty ipAddress. This patch fixes this issue by ensuring that we
wait until a POD gets an IPAddress and process it only after one
is assigned to it.
Fixes issue: #331
Signed-off-by: Sridhar Gaddam sgaddam@redhat.com