systemvm: for ip route show command don't use the throw command

[yadvr]

While searching for existing route, don't use the throw keyword when
using the cmd with ip route show. This fixes unnecessary ERROR messages in the VR cloud.log and issue of re-adding an already added routing rule (which may throw RTLINK file already exists error).

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)

[yadvr]

@blueorangutan package

[blueorangutan]

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

[blueorangutan]

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-301

[yadvr]

@blueorangutan test

[blueorangutan]

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[blueorangutan]

Trillian test result (tid-395)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 29386 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr3612-t395-kvm-centos7.zip
Smoke tests completed. 77 look OK, 0 have error(s)
Only failed tests results shown below:

Test	Result	Time (s)	Test File

[yadvr]

Can you review this @ustcweizhou ? Thanks.

[ustcweizhou]

LGTM
tested in vpc, no issues.

[yadvr]

@andrijapanicsb can you review? this is the bug that cause errors in the /var/log/cloud.log for a VR when it runs command to show/check if a route exists (doesn't actually cause any VR issues/failure, but causes errors in the log)

[yadvr]

@andrijapanicsb can you review this? Thanks.

[andrijapanicsb]

LGTM - tested manually, and the specific error is not there.