Comment 7 for bug 1962599

Thank you George for all the help ! Removing field critical. I'm still unsure what part of the deployment added the routing rule to BondM. I think it's part of the default configuration by MAAS. A permanent workaround is to use the advanced-policy-routing charm to add the correct routing to the calico network. I believe this should be added by default to our deployment templates on baremetal. Example :

With 192.168.20.0/24 the OAM network and 10.128.0.0/16 the calico network.

  advanced-policy-routing:
    charm: cs:advanced-routing
    options:
      action-managed-update: False
      enable-advanced-routing: True
      advanced-routing-config: |
        [ {
            "type": "table",
            "table": "SF1"
        }, {
            "type": "route",
            "default_route": true,
            "gateway": "10.147.254.1",
            "table": "SF1"
        }, {
            "type": "rule",
            "from-net": "192.168.20.0/24",
            "to-net": "10.128.0.0/16",
            "priority": 0
        }, {
            "type": "rule",
            "from-net": "10.128.0.0/16",
            "table": "SF1",
            "priority": 100
        } ]