Bug 1305880 - [RFE] - Enable changing the bootproto from dhcp to static manually on the host, after host was added to engine
[RFE] - Enable changing the bootproto from dhcp to static manually on the hos...
Status: CLOSED WONTFIX
Product: ovirt-engine
Classification: oVirt
Component: RFEs (Show other bugs)
3.6.3
x86_64 Linux
unspecified Severity medium (vote)
: ---
: ---
Assigned To: Rob Young
Gil Klein
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-09 08:32 EST by Michael Burman
Modified: 2018-06-06 03:46 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-06-06 03:46:06 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Network
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
ylavi: ovirt‑future?
mburman: planning_ack?
mburman: devel_ack?
mburman: testing_ack?


Attachments (Terms of Use)

  None (edit)
Description Michael Burman 2016-02-09 08:32:07 EST
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 08:32:32 EST
Also see related BZ - 1296144
Comment 2 Yaniv Lavi 2018-06-06 03:46:06 EDT
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.