Vnet_route_check TCP socket for DB connection. #3578
Merged
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.
Currently the Vnet_route_check fails if a user calls it witout sudo with the following error.
What I did
The route_check script accesses the same DB tables but is able to run without the sudo rights. To solve this problem I have changed the Vnet_route_check to use a TCP socket to connect to the DB as done in route_check. As a result the script doesn't fail with a run time error.
How I did it
How to verify it
create a new user on a T1 device which has no docker or sudoers privilage. run vnet_route check. it should fail.
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)
None