+++ This bug was initially created as a clone of Bug #989349 +++
Description of problem:
Configuring bad network configuration causes rollback (as expected) but we get "unexpected internal engine error" message as a result of rollback
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Cause "check connectivity failure" (for example by configuring another network in the subnet of rhevm manager)
2. Check connectivity will fail and rollback will take place (2 min by default)
3.
Actual results:
We get "Unexpected internal error message", though an action of revert succeeded
Expected results:
More clear message should be displayed:
For example:
Reverting back to orignal configuration as check connectivity failed
Additional info:
--- Additional comment from GenadiC on 2014-03-04 02:31:47 EST ---
Internal error appears if you configure additional network in the same subnet as the MGMT network after reverting back from "check connectivity" failure
This is an automated message
oVirt 3.4.1 has been released:
* should fix your issue
* should be available at your local mirror within two days.
If problems still persist, please make note of it in this bug report.