Bug 1277988

Summary:	[vdsbroker] Ignore heartbeat when running setupNetworks
Product:	[oVirt] ovirt-engine	Reporter:	Piotr Kliczewski <pkliczew>
Component:	Backend.Core	Assignee:	Piotr Kliczewski <pkliczew>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.0.0	CC:	bugs, oourfali, pkliczew
Target Milestone:	ovirt-4.1.0-alpha	Flags:	oourfali: ovirt-4.1? rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-27 12:13:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Piotr Kliczewski 2015-11-04 13:43:11 UTC

Description of problem:

Currently when setupNetworks is executed we negotiate heartbeat policy before and after the operation. As a result we drop and create new connection twice.
There are situations that after successful run of the setupNetworks due to connection reset the host is in Connecting state for short period of time.

Version-Release number of selected component (if applicable):


How reproducible:
We need to run setupNetworks serveral time and it is matter of timing that we see this issue.

Steps to Reproduce:
1.
2.
3.

Actual results:
Host changes status to Connecting for short period of time.


Expected results:
Host status should not be changed if setupNetworks operation was successful.

Additional info:
We need to ignore heartbeats on the engine side without negotiations.

Comment 2 Dan Kenigsberg 2016-01-26 08:03:15 UTC

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

Comment 3 Sandro Bonazzola 2016-05-02 09:58:42 UTC

Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.

Comment 4 Yaniv Lavi 2016-05-23 13:15:40 UTC

oVirt 4.0 beta has been released, moving to RC milestone.

Comment 5 Yaniv Lavi 2016-05-23 13:19:29 UTC

oVirt 4.0 beta has been released, moving to RC milestone.

Comment 6 Oved Ourfali 2016-05-25 14:15:13 UTC

It would have been nice to have that in 4.1.
However, after it took us a lot of time to get host deploy + setup networks stabilized in 4.0/3.6, I suggest to postpone to 4.1, and do it early in the 4.1 development phase.

Comment 7 Oved Ourfali 2016-11-27 12:13:27 UTC

This is the reconnect changes.
Closing as duplicate.

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