<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 15, 2016 at 3:50 PM, Yedidyah Bar David <span dir="ltr"><<a href="mailto:didi@redhat.com" target="_blank">didi@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On Mon, Feb 15, 2016 at 4:22 PM, Mike DePaulo <<a href="mailto:mikedep333@gmail.com">mikedep333@gmail.com</a>> wrote:<br>
> Hi,<br>
><br>
> I am getting the following error when I attempt to setup my 2nd ovirt<br>
> node as a hosted-engine:<br>
><br>
> RuntimeError: The selected device None is not a supported bridge port<br>
><br>
> The 1st node is death-star (192.168.1.50)<br>
> The 2nd node is starkiller-base (192.168.1.52)<br>
><br>
> This is not a production environment; this is my apartment.<br>
><br>
> I am able to access the engine's webGUI.<br>
><br>
> Both death-star and starkiller-base start out with only eno1 as their only NIC.<br>
> death-star, by the end of the hosted-engine-setup, had ovirtmgmt also<br>
> (with the same MAC address.)<br>
> starkiller-base does not have ovirtmgmt yet.<br>
> I am not using VLANs.<br>
><br>
> node version: ovirt-node-iso-3.6-0.999.201602121021.el7.centos.iso<br>
> engine appliance version: oVirt-Engine-Appliance-CentOS-x86_64-7-20160126.ova<br>
<br>
</span>Seems like a bug in [1] - seems like we do not configure the bridge anymore<br>
on additional host. But I didn't yet try that myself, I might be missing<br>
something. Adding Simone.<br>
<br>
[1] <a href="https://gerrit.ovirt.org/#/q/Ifcff652ef28e6b912514df2dd2daac2b07eca61e,n,z" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/#/q/Ifcff652ef28e6b912514df2dd2daac2b07eca61e,n,z</a><br>
<span class=""><font color="#888888">--<br>
Didi<br>
</font></span></blockquote></div><br></div><div class="gmail_extra">Yes, it was a real bug: <a href="https://gerrit.ovirt.org/#/c/53428/">https://gerrit.ovirt.org/#/c/53428/</a> should address it.</div><div class="gmail_extra">It should be available in tomorrow build.</div></div>