/etc/network/interfaces broken in 17.04.

Bug #1676362 reported by Lasse
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Expired
Undecided
Unassigned

Bug Description

I upgraded from 16.10 to 17.04 final beta (at 26th of Mars). When upgrading, my working settings from 16.10 did not work anymore.

My main configuration:

auto eno1
iface eno1 inet manual
bond-master bond0

auto eno2
iface eno2 inet manual
bond-master bond0

auto bond0
iface bond0 inet manual
        #bond-mode 802.3ad
        bond-mode 4
        bond-miimon 100
        bond-lacp-rate 1
        bond-slaves eno1 eno2

Then I have a bunch of tagged virtual "switches" for use from my VM:

auto bond0.664
iface bond0.664 inet manual
        vlan-raw-device bond0

auto service0
iface service0 inet manual
        bridge_ports bond0.664

Sadly I am not able to give a lot of information because this was noticed on a production server I tried to upgrade during the weekend. This server had some performance issues with ZFS and I wanted to see if newer version of ZFS would solve the problem. When this network problem was found, I had time for nothing else than to roll back the system to the snapshot I did before upgrading.

The only information I have is that I could not reach the servers running through some of these switches (for example the one pasted above). When downgrading back to 16.10, everything worked again.

Tags: bot-comment
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1676362/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue using a maintained version of Ubuntu then please let us know otherwise this report can be left to expire in approximately 60 days time.

Paul White
[Ubuntu Bug Squad]

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu because there has been no activity for 60 days.]

Changed in ubuntu:
status: Incomplete → Expired
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.