Bug 1305880 - [RFE] - Enable changing the bootproto from dhcp to static manually on the host, after host was added to engine
Summary: [RFE] - Enable changing the bootproto from dhcp to static manually on the hos...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: 3.6.3
Hardware: x86_64
OS: Linux
unspecified
medium vote
Target Milestone: ---
: ---
Assignee: Rob Young
QA Contact: Gil Klein
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-09 13:32 UTC by Michael Burman
Modified: 2018-06-06 07:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-06 07:46:06 UTC
oVirt Team: Network
ylavi: ovirt-future?
mburman: planning_ack?
mburman: devel_ack?
mburman: testing_ack?

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.