[systemd-bugs] [Bug 80007] New: systemd-networkd: networkd can't create bond from 2 auto configured interfaces post-boot
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Jun 13 16:37:07 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=80007
Priority: medium
Bug ID: 80007
Assignee: systemd-bugs at lists.freedesktop.org
Summary: systemd-networkd: networkd can't create bond from 2
auto configured interfaces post-boot
QA Contact: systemd-bugs at lists.freedesktop.org
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: spkane00 at gmail.com
Hardware: All
Status: NEW
Version: unspecified
Component: general
Product: systemd
CoreOS related bug filing:
https://github.com/coreos/bugs/issues/36
Using cloud-init to setup network and netdev units for bonded interfaces does
not work as expected, since networkd does not ifdown interfaces that it did not
setup.
This means that a physical system with 2 nics that is netbooted with a plain
CoreOS image will have those interfaces setup during boot automatically by
udev(?) and when cloud-init sets up a bond and then restarts networkd,
networkd, does not ifdown eno1 and eno2, which means they can not be enslaved
to the bond and things fail to come up properly.
networkd could likely continue to ignore devices it knows nothing about, but
assume that it is safe to down interfaces that it now has configuration for,
even if it didn't initially bring them up.
A bit more documentation:
https://gist.github.com/spkane/8f117f67533822b2481f
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140613/2497943f/attachment.html>
More information about the systemd-bugs
mailing list