<div dir="ltr">Dan,<div><br></div><div>Thanks for the information. I'll follow that RFE. Being able to re-provision a host and not have to remember the correct network interface mapping for 10 interfaces would be a huge help...too much can go wrong if I have to re-setup a config that I thought was saved in the engine.</div><div><br></div><div>Thanks,</div><div>- Trey</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 22, 2015 at 3:35 AM, Dan Kenigsberg <span dir="ltr"><<a href="mailto:danken@redhat.com" target="_blank">danken@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Sat, Jun 20, 2015 at 12:28:10PM -0500, Trey Dockendorf wrote:<br>
> I recently found that when I reinstall a VDSM host via the engine<br>
> interface, if that host was actually re-provisioned via kickstart, the<br>
> network settings defined in the engine are lost. Before the re-install I<br>
> had defined 4 bonds and attached 5 logical networks to the host. After a<br>
> re-install only ovirtmgmt was attached to the node. Is it intended<br>
> behavior that a host's network configuration in the ovirt-engine be lost<br>
> when a host is re-provisioned ? If I have to re-deploy a node, is there a<br>
> way to make the ovirt-engine define networks for that host get applied to<br>
> the re-deployed system?<br>
<br>
</div></div>Yes, this is the inteded behavior, though some consider this a design<br>
bug. Network config is persisted on each host, and Engine do not<br>
automatically applies its own definitions ona re-provisioned host,<br>
however, we have<br>
<br>
1194297 [RFE] Allow to synchronize all networks on an<br>
out-of-sync host<br>
<br>
in the works, which would make life easier in such conditions.<br>
<span class="HOEnZb"><font color="#888888"><br>
Dan.<br>
</font></span></blockquote></div><br></div>