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.