Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
provider/maas: remove MTU option from the bridge options #5791
Conversation
|
$$merge$$ $$fixes-1584616$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
jujubot
merged commit d836575
into
juju:master
Jul 14, 2016
voidspace
referenced this pull request
Aug 17, 2016
Merged
provider/maas: remove MTU option from the bridge (backport) #6013
added a commit
that referenced
this pull request
Aug 19, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
frobware commentedJul 13, 2016
•
Edited 1 time
-
ericsnowcurrently
Jul 13, 2016
The MTU statement must be on the interface to work and not on the bridge
itself; bridges inherit the lowest MTU of all sub-interfaces. Further to
this, ifupdown seems to bug out and always fails to add the default
route when an MTU is set on the bridge. Leaving the MTU option on the
bridge completely breaks the network on reboot.
This commit also removes:
address
gateway
netmask
dns-nameservers
dns-search
dns-sortlist
from the sub-interfaces, leaving them on the bridge interface only.
Fixes LP:#1584616
(Review request: http://reviews.vapour.ws/r/5234/)