fix(routetable): fix panic on sorting both v4 and v6 routes #1279
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.
This is just a rebase + conflict resolution of PR #893 which appears to be abandoned. Credit for this fix should go to @vaspahomov.
Signed-off-by: vaspahomov vas2142553@gmail.com
Signed-off-by: Jesse Suen jessesuen@gmail.com
Description of your changes
Fixes #795
I have:
make reviewable test
to ensure this PR is ready for review.How has this code been tested
I was encountering the panic in #795 when creating route tables in a VPC with ipv6 enabled. The panic causes the provider-aws controller to crashloop and will not recover. With this fix, the panic no longer happens.