Bug 1305880

Summary: [RFE] - Enable changing the bootproto from dhcp to static manually on the host, after host was added to engine
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: RFEsAssignee: Rob Young <royoung>
Status: CLOSED WONTFIX QA Contact: Gil Klein <gklein>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.6.3CC: bugs, ylavi
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: ylavi: ovirt-future?
mburman: planning_ack?
mburman: devel_ack?
mburman: testing_ack?
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-06 07:46:06 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:

Description Michael Burman 2016-02-09 13:32:07 UTC 
Description of problem:
[RFE] - Enable changing the bootproto from dhcp to static manually on the host, after host was added to engine.
 
- Currently engine will return to what was configured first with the setupNetworks received by vdsm.  
It means, that when host was added to engine, the setupNetworks received by vdsm
configured the host with dhcp(if wasn't changed before), and every change that was done manually on the host, engine will return to what vdsm reports and configured when host was added to engine, to dhcp. 

Scenario:

1. Install clean host with dhcp
2. Add host to engine
3. On host, manually change the bootproto to static/none
4. Refresh caps on host via engine and see that wrong bootproto is reported by vdsm, dhcp as enabled.
Comment 1 Michael Burman 2016-02-09 13:32:32 UTC 
Also see related BZ - 1296144
Comment 2 Yaniv Lavi 2018-06-06 07:46:06 UTC 
Closing old RFEs, please reopen if still needed.
Patches are always welcomed.