Static routes get default gateway instead of routed gateway

Bug #2060144 reported by james beedy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Undecided
Unassigned

Bug Description

Hello,

I am facing some unexpected behavior where MAAS does not create the correct static routes.

I have configured a static route for 10.0.8.0/22 via 192.168.7.254.

MAAS neglects my route and creates the route using default gateway for the subnet, instead of my static route. See screen shots

This is a severe bug and blocking our prod deployments. Any help would be greatly appreciated. Thanks.

Revision history for this message
james beedy (jamesbeedy) wrote :
Revision history for this message
james beedy (jamesbeedy) wrote :
Revision history for this message
Jacopo Rota (r00ta) wrote :

Hi,

Which version are you using?

Revision history for this message
Jacopo Rota (r00ta) wrote :

Also, which ubuntu image are you deploying?

Revision history for this message
james beedy (jamesbeedy) wrote :

I think it’s happening because I’ve selected to enable the new dhcp server when initializing maas.

Happening on both 3.4 and 3.5.

Revision history for this message
Jacopo Rota (r00ta) wrote (last edit ):

tried on 3.5 (under development) and ubuntu 20.04 and it works fine on my end. We need more data to reproduce. Marking this as invalid until more information are provided

Changed in maas:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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