<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - systemd-networkd: networkd can't create bond from 2 auto configured interfaces post-boot"
href="https://bugs.freedesktop.org/show_bug.cgi?id=80007#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - systemd-networkd: networkd can't create bond from 2 auto configured interfaces post-boot"
href="https://bugs.freedesktop.org/show_bug.cgi?id=80007">bug 80007</a>
from <span class="vcard"><a class="email" href="mailto:sam@packet.net" title="sam@packet.net">sam@packet.net</a>
</span></b>
<pre>To add a little more color to this issue, that I am also affected by, it is
very common to have the interfaces up when attempting to apply a new
configuration, many times it is the only way.
For example, a common server provisioning workflow might be:
Power On
DHCP single interface
tftp and pxeboot into the OS
Cloud-init writes the .network and .netdev files to the appropriate locations
restart networking to come up with bonding
With this current issue the network restart doesn't create the bond as desired.
For now, as a workaround, I'm adding a tiny bash script that does this during
the provisioning sequence, but would love to see a fix to this in the future.
Thanks.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>