Bug 1296144

Summary:	vdsm keeps reporting dhcp lease although it was changed to static ip
Product:	[oVirt] vdsm	Reporter:	Michael Burman <mburman>
Component:	General	Assignee:	Edward Haas <edwardh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.17.14	CC:	bugs, danken
Target Milestone:	ovirt-4.0.0-alpha	Flags:	rule-engine: ovirt-4.0.0+ rule-engine: planning_ack+ danken: devel_ack+ rule-engine: testing_ack+
Target Release:	4.17.999
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt 4.0.0 alpha1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-05 07:38:48 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-01-06 12:50:26 UTC

Description of problem:
vdsm keeps reporting dhcp lease although it was changed to static ip.

When changing the bootproto from dhcp to static ip via the command line on the server, vdsCaps continue to report the dhcp lease and will not recognize the change, although the server now have static ip. 

Version-Release number of selected component (if applicable):
vdsm-4.17.15-0.el7ev.noarch

How reproducible:
100

Steps to Reproduce:
1. Install clean rhel 7.2 server with vdsm-4.17.15-0.el7ev.noarch and obtain ip via dhcp server
2. Via ifcfg-* change the bootproto to none/static and set a static ip instead of dhcp
3. Restart network service

Actual results:
vdsm keeps reporting the dhcp lease.
If installing the server in rhev-m it will configure the 'ovirtmgmt' bridge with bootproto=dhcp and not static as should. 

Expected results:
vdsm should report static ip

Comment 1 Edward Haas 2016-02-09 11:37:37 UTC

One small remark for clarity:
The patch fixes the described scenario, when no setupNetworks is received by vdsm.
After a successful setupNetworks, vdsm will report the dhcp status as seen in the running configuration and not the actual.

Maybe this scenario deserves its own ticket:
1. Install new host (with dhcp).
2. Add host in engine. (running config is created)
3. In the host, change manually to static ip (and apply).
4. Issue get caps report and see wrongs dhcp as enabled.

Comment 2 Michael Burman 2016-02-09 13:33:08 UTC

(In reply to Edward Haas from comment #1)
> One small remark for clarity:
> The patch fixes the described scenario, when no setupNetworks is received by
> vdsm.
> After a successful setupNetworks, vdsm will report the dhcp status as seen
> in the running configuration and not the actual.
> 
> Maybe this scenario deserves its own ticket:
> 1. Install new host (with dhcp).
> 2. Add host in engine. (running config is created)
> 3. In the host, change manually to static ip (and apply).
> 4. Issue get caps report and see wrongs dhcp as enabled.

This scenario have now it's own BZ - 1305880

Comment 3 Michael Burman 2016-04-07 07:23:26 UTC

Verified on - vdsm-4.17.999-892.git435139d.el7.centos.noarch

Comment 4 Sandro Bonazzola 2016-07-05 07:38:48 UTC

oVirt 4.0.0 has been released, closing current release.