MAAS

Default gateway (per-subnet) should have a metric value

Bug #1674866 reported by Mike Pontillo
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Wishlist
Unassigned
MAAS 2.3.x

Bug Description

Right now, MAAS correctly models static routes with a 'metric' value. On deployment, every static route can be added to the kernel, and if there is a conflict the route with the lowest metric is selected.

The default gateway is a route. It just happens to be a special case route of least preference (because it has the shortest possible prefix length). Even least-preference routes should be able to have a metric, for two reasons:

 - In case we want to add every default gateway to the kernel, then the kernel will know which one to select in case of an unreachable gateway.

 - In case we can only add one gateway, we can pick the lowest-metric route to supply to the deployment.

Andres Rodriguez (andreserl)
Changed in maas:
importance: Undecided → Wishlist
status: New → Triaged
milestone: none → 2.2.0
milestone: 2.2.0 → next
Andres Rodriguez (andreserl)
Changed in maas:
milestone: next → 2.3.0
Andres Rodriguez (andreserl)
Changed in maas:
milestone: 2.3.0 → 2.3.x
Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Triaged → Invalid
Revision history for this message
Peter Sabaini (peter-sabaini) wrote :

I've come across this -- we have two subnets in spaces, each with a gw. This results in two default routes like these:

default via 10.0.0.1 dev eth1 proto static
default via 10.0.1.1 dev eth0 proto static

We should have a metric here to be able to explicitly prio default routes

Changed in maas:
status: Invalid → New
Revision history for this message
Alberto Donato (ack) wrote :

This is a valid feature request.

We currently track feature requests in the "Feature" category on our discourse at https://discourse.maas.io/c/features

Please make a post there so we can track discussion.

Changed in maas:
status: New → Invalid
Revision history for this message
Rafael (rvallel) wrote :

2 default gateways without the ability to set priority lead to obscure network issues.
This bug affects me too, and not many others because not everyone uses more than one network during deployment.

Also notice that the current workaround, available at the maas forum, is to completely remove the default gateway in one of the MAAS network configurations, that will lead to only one default gateway on the deployed system, and one a half networks working.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.