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.
*** Bug 1277991 has been marked as a duplicate of this bug. ***
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
oVirt 4.0 beta has been released, moving to RC milestone.
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.
This is the reconnect changes. Closing as duplicate. *** This bug has been marked as a duplicate of bug 1388778 ***