Description of problem: Remove Bootproto and IP from NIC's tooltip on setup network. Bootproto and IP should be displayed in the network's tooltip and not on the NIC's tooltip as it today. Version-Release number of selected component (if applicable): 3.6.0-0.18.el6
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
oVirt 4.0 beta has been released, moving to RC milestone.
Michael, if the NIC is not (yet) attached to a network, it makes sense to see Bootproto/IP on its tooltip. Do you see the bootproto even when the NIC is attached to a VM network or a bond? (screenshot would be nice)
(In reply to Dan Kenigsberg from comment #4) > Michael, if the NIC is not (yet) attached to a network, it makes sense to > see Bootproto/IP on its tooltip. > Do you see the bootproto even when the NIC is attached to a VM network or a > bond? (screenshot would be nice) Yes, on the nic/bond
Created attachment 1205195 [details] nic screen shot
Created attachment 1205196 [details] bond screenshot
I was expecting that part of this change the IP will be reported on the network's tooltip and not only the bootproto. Currently we only display the bootproto on the network's tooltip as part of this change, but the IP should have been added as well(without the need to edit the network). I would like this be handled as part of this report as it should be. - Another thing should be handled as part of this fix, we still report bootproto on top of the slaves, if the NIC is bond.
Created attachment 1321434 [details] record1
Ales, we are almost there, almost everything has been fixed and looks great, the only thing that is still not reported properly are vlan networks, when the network is vlan and it has dhcp/static bootproto, you report it as 'none'. Except this, everything great.
Created attachment 1326912 [details] new record for vlan networks
Verified on - 4.2.0-0.0.master.20170929123516.git007c392.el7.centos
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.