[action] [PR:3244] [dualtor_neighbor_check] Fix the script not exists issue (#3244) #3251
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
) What I did Fix sonic-net/sonic-buildimage#17200 Microsoft ADO (number only): 27317600 Upon advanced-reboot, the Lua script is flushed, so the EVALSHA command might suffer from the script not-existed issue. Let's check if the script exists before calling EVALSHA. Signed-off-by: Longxiang Lyu [email protected] How I did it As the above. How to verify it UT and verify on dualtor testbed. Previous command output (if the output of a command-line utility has changed) New command output (if the output of a command-line utility has changed)
|
Original PR: #3244 |
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.
What I did
Fix sonic-net/sonic-buildimage#17200
Microsoft ADO (number only): 27317600
Upon advanced-reboot, the Lua script is flushed, so the EVALSHA command
might suffer from the script not-existed issue. Let's check if the
script exists before calling EVALSHA.
Signed-off-by: Longxiang Lyu [email protected]
How I did it
As the above.
How to verify it
UT and verify on dualtor testbed.
Previous command output (if the output of a command-line utility has changed)
New command output (if the output of a command-line utility has changed)