Comment 1 for bug 1538757
Revision history for this message
| Matthew Mosesohn (raytrac3r) wrote Re: [fuelmenu] Default gateway set to None on 'Apply' action | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
Oleg, I can't reproduce this in my local environment, but I can tell you here's how the gateway feature works:
1 - If you modify a network interface where the gateway is currently set, it gets unset (so we can apply a new one)
or if it's a DHCP interface, we also unset gateway manually.
However, if you have eth1 with a gateway, then configure eth0 gateway, eth1's gateway stays. You must unset eth1's gateway before eth0's gateway becomes the default. The highest interface # wins in this case.
2 - we run l23network in Puppet to apply config changes. This ultimately sets the new gateway.
A new default gateway is left as None if the new config can't ping that gateway. That leads me to think that it's your network.
I need you to provide logs and if possible, access to your env to see this in action. There are logs in /var/log/puppet and /var/log/