route show on new data doesn't have default route on mgmt interfaces

[jopietsch]

Describe the bug
I don't know if this is a bug or this is on purpose

this is what I currently get

(suzieq-ITL68y-d-py3.7) jpiet@b2:~/suzieq$ python suzieq/cli/suzieq-cli -c ~/multidc.yml route show --namespace='ospf-ibgp' --hostname='leaf01'
 --vrf=mgmt
   namespace hostname   vrf                                prefix nexthopIps  ...          source metric ipvers   action               timestamp2  ospf-ibgp   leaf01  mgmt  IPNetworkArray(['192.168.121.0/24'])         []  ...  192.168.121.55     20      4  forward 2020-06-15 02:38:13.496
[1 rows x 12 columns]

What I get from data and suzieq that's about a week old

(suzieq-ITL68y-d-py3.7) jpiet@a2:~/suzieq-old$ python3 suzieq/cli/suzieq-cli -c ~/multidc-old.yml route show --namespace="ospf-ibgp" --hostname='leaf01'  --vrf=mgmt
   namespace hostname   vrf            prefix       nexthopIps  ...           source metric ipvers   action               timestamp
0  ospf-ibgp   leaf01  mgmt         0.0.0.0/0  [192.168.121.1]  ...                      20      4  forward 2020-04-27 02:11:25.664
3  ospf-ibgp   leaf01  mgmt  192.168.121.0/24               []  ...  192.168.121.115     20      4  forward 2020-04-27 02:11:25.664

[2 rows x 12 columns]

If I run the old (week old) code on the new data, I also do not see the default, so it looks like what changes is on the sq-poller side.

[aegiacometti]

may a thing on the tfsm templates?

[ddutt]

Linux routing-table specific issue. We exclude routes with a metric of 4278198272. In reality we should exclude these only if there are no other equivalent routes with a better metric.