Reviewed: https://review.openstack.org/396770
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=7647e3e56f630708ad4da12ba1af429d49ac1fc1
Submitter: Jenkins
Branch: master
commit 7647e3e56f630708ad4da12ba1af429d49ac1fc1
Author: Omer Anson <omer.an...@toganetworks.com>
Date: Tue Nov 8 18:08:50 2016 +0200
Parse the output of ip route more robustly
The code parsing the output of ip route assumes that the output is the
destination network, and then key/value pairs. This is not necessarily
the case, as the output may contain flags.
This change modifies the parsing of ip route's output to look
specifically for the keys of interest, and read their values
exclusively.
Change-Id: I34b6c0afb05550c970b1cacda8ec472294215403
Closes-Bug: 1640008
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1640008
Title:
Getting routing table by parsing 'ip route' command fails on xenial
Status in neutron:
Fix Released
Bug description:
Getting routing table by parsing 'ip route' command fails on Ubuntu
Xenial.
The code assumes that ip route command returns the network, and then
key-value pairs of data of the routing record. In xenial, it can be
seen that ip also adds some flags at the end, e.g. linkdown.
A reproduction of this failure can be seen on the gate, via 'check
experimental'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1640008/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
