Created attachment 991885 [details] logs and ifcfg files Description of problem: Wrong BOOTPROTO displayed on SN GUI. I have attached VM network to physical NIC on host that has BOOTPROTO=dhcp, Then i changed via the ifcfg files the NIC and the bridge BOOPROTO to none and restarted network service. But SN is still displaying the NIC and the VM network attached to him as DHCP, it's wrong displaying, cause the ifcfg files has changed to none(NIC's and bridge), they have no BOOTPROTO, but GUI displaying they have DHCP BOOTPROTO. If trying to change the VM network to none via SN it seems to work, but entering to SN after approving operation will still display the NIC and the network as DHCP BOOTPROTO. Version-Release number of selected component (if applicable): 3.6.0-0.0.master.20150214002157.gitbb45d00.el6
Created attachment 991886 [details] screenshot 1
Created attachment 991887 [details] screenshot 2
So the issue is much worse, cause it's not possible to change the BOOTPROTO via SN, and every try to change the network from dhcp to none will cause the network to get ip, and it's really bad. In case of rhevm on NIC1 and other VM network on NIC2 that will get the ip in situation described above, will cause the host to loose connectivity and go to non-responsive state. Another thing i noticed is that vdsCaps report: 'mic5': {'addr': '', 'bridged': True, 'cfg': {'BOOTPROTO': 'dhcp', ifcfg files with none on the BOOTPROTO, vdsStats report: doesn't display mic5 network brctl show doesn't display 'mic5' bridge. When this network 'mic5' is actually attached to the host NIC.
Created attachment 991930 [details] Logs
I do not think we need to track this independently of bug 1184497. *** This bug has been marked as a duplicate of bug 1184497 ***