This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
*** Bug 1648987 has been marked as a duplicate of this bug. ***
This needs to be retested because things changed on hosted-engine restore procedure
(In reply to Sandro Bonazzola from comment #9) > This needs to be retested because things changed on hosted-engine restore > procedure Please update this bug when the procedure is retested. Also, Simone says in comment 0: > In that case we are *pretty* sure that the deployment will correctly conclude and the user can successfully connect the engine. As of now, are we *sure* that the deployment will correctly conclude and the user can successfully connect the engine?
Simone can you pelase retest this flow?
Evgeny, can you please retest this flow?
Considering that this bug has been untested after more than a year of requesting, I am taking the approach that this is not really that important and so I am closing this as WILLNOTFIX. If you disagree, please reopen with a comment.
If we are going to not fix this, it's not going to land in 4.4.4. Dropping target.