Looks like a local issue, or a temporary one as no-one else have hit it.
And zesty is now off.
** Changed in: ifupdown (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After you change your /e/n/i to that, and reproduce the issue,
break=init, and then mount -oremount,rw /root; chroot /root; vi
/etc/network/interfaces and comment out everything from "auto br1" to
end of file, exit; mount -oremount,ro /root; exit
and you're back to a bootable system... Which is
The reboot of the system prior to this morning was after a dist-upgrade
on "2016-10-14 08:30:10" according to /var/log/apt/history.log -- the
upgrade to zesty occurred on 2016-10-18, and the reboot was after a
fresh dist-upgrade this morning, on zesty.
--
You received this bug notification
** Attachment added: "/e/n/i that results in a loop"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1635654/+attachment/4764881/+files/interfaces
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
