Bug 820976

Summary: [RHEVM] [GUI] [webadmin] [Setup Host Networks] changing rhevm NIC automatically configured Boot Protocol to "none".
Product: Red Hat Enterprise Virtualization Manager Reporter: Martin Pavlik <mpavlik>
Component: ovirt-engineAssignee: Muli Salem <msalem>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Pavlik <mpavlik>
Severity: high Docs Contact:
Priority: high    
Version: 3.1.0CC: dyasny, ecohen, gklein, iheim, lpeer, Rhev-m-bugs, yeylon, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-06 07:07:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot rhevm_em1.png
none
screenshot rhevm_em2.png none

Description Martin Pavlik 2012-05-11 13:19:53 UTC 
Description of problem:
if rhevm NIC is changed Boot Protocol = none (see screenshot rhevm_em2.png) this should be not allowed, rhevm interface has to have either Boot Protocol = Static or Boot Protocol = DHCP

Version-Release number of selected component (if applicable):
oVirt Enterprise Virtualization Engine Manager Version: 3.1.0_0001-9.el6ev 

How reproducible:
100%

Steps to Reproduce:
1.Hosts -> your host (in maintenance) -> Setup Hosts network (for detailed settings see screenshot rhevm_em1.png)

2.Drag rhevm network to some different NIC (e.g. em2) -> click the pencil icon of the interface where you dragged rhevm network (see screenshot rhevm_em2.png)

  
Actual results:
Boot Protocol = none

Expected results:
rhevm interface has to have either Boot Protocol = Static or Boot Protocol = DHCP

Additional info:
Comment 1 Martin Pavlik 2012-05-11 13:20:51 UTC 
Created attachment 583842 [details]
screenshot rhevm_em1.png
Comment 2 Martin Pavlik 2012-05-11 13:21:33 UTC 
Created attachment 583843 [details]
screenshot rhevm_em2.png
Comment 3 lpeer 2012-05-18 07:25:45 UTC 
before blocking this we should look into all-in-one scenario and see if we really need an IP for the communication between the manager and the host. Does registering a host with 127.0.0.1 work?
Comment 4 Muli Salem 2012-08-05 13:26:46 UTC 
Adding to that - 

SetupNetworks flow changed so that when rhevm NIC is changed Boot Protocol does not change, but rather stays the same.

In addition, Boot Protocol None is greyed out when dealing with mgmt network.

It seems the only way to set Boot Protocol=none is through REST, perhaps this option should be kept for admins to use.
Comment 5 lpeer 2012-08-06 06:57:11 UTC 
(In reply to comment #4)
> Adding to that - 
> 
> SetupNetworks flow changed so that when rhevm NIC is changed Boot Protocol
> does not change, but rather stays the same.
> 
> In addition, Boot Protocol None is greyed out when dealing with mgmt network.
> 
> It seems the only way to set Boot Protocol=none is through REST, perhaps
> this option should be kept for admins to use.

I agree, Martin can you please confirm the described above is the status?
Comment 6 Martin Pavlik 2012-08-06 07:04:44 UTC 
Yes, I confirm. What is next? Closed current release?
Comment 7 lpeer 2012-08-06 07:07:34 UTC 
(In reply to comment #6)
> Yes, I confirm. What is next? Closed current release?

yes thank you.