Bug 999947

Summary:	[RFE] Refresh Network configuration periodically
Product:	[oVirt] ovirt-engine	Reporter:	Moti Asayag <masayag>
Component:	RFEs	Assignee:	Scott Herold <sherold>
Status:	CLOSED DUPLICATE	QA Contact:	Meni Yakove <myakove>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.4.0	CC:	bazulay, bugs, danken, gcheresh, iheim, lpeer, nyechiel, rbalakri, reliezer, yeylon, ylavi
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	ylavi: ovirt-future? rule-engine: planning_ack? danken: devel_ack+ rule-engine: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	network
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-01-27 09:29:53 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:
Bug Depends On:
Bug Blocks:	988469, 1058499

Description Moti Asayag 2013-08-22 12:18:37 UTC

Description of problem:
Network changes manually applied on the host are not reflected to the engine unless the host is being manually refreshed using the refresh capabilities. This might lead to lack of synchronization between the current host configuration as recently collected to the current configuration on the host (e.g. manual changes performed on the host not via the setupNetworks api).

Comment 1 Moti Asayag 2013-08-25 21:41:04 UTC

Another motivation of having a monitor for refreshing the network configuration is the race between the network information collection to the IP address which is being obtained from the DHCP server:

It is not rare to see setupNetworks configures an interface for DHCP, and the immediate getVdsCaps which follows doesn't report any IP address for that interface due to latency of the DHCP server.

Having the monitor to auto-refresh such configuration will simplify the fix of bug 955429, prevent run a VM if the display network has no IP address.

Comment 3 Moti Asayag 2014-04-30 21:06:21 UTC

*** Bug 1093046 has been marked as a duplicate of this bug. ***

Comment 5 Yaniv Lavi 2015-04-05 16:01:03 UTC

Is this similar to bz #1037612?

Comment 6 Lior Vernia 2015-04-06 07:34:57 UTC

No.

Comment 7 Yaniv Lavi 2016-01-27 09:29:53 UTC


*** This bug has been marked as a duplicate of bug 1240719 ***

Comment 8 Bell Levin 2019-01-31 10:13:10 UTC

*** Bug 1667181 has been marked as a duplicate of this bug. ***