Created attachment 1339590 [details] engine log Description of problem: Can't re-install host - engine complaining that 'The provider type should be 'OpenStack Networking'. - If trying to re-install host on master we are blocked because of a new regression caused by network team - Error while executing action: "silver-vdsb.qa.lab.tlv.redhat.com: Cannot edit Host. The provider type should be 'OpenStack Networking'." 2017-10-17 09:44:05,316+03 WARN [org.ovirt.engine.core.bll.hostdeploy.InstallVdsCommand] (default task-2) [ad550f50-b477-4811-99ee-52e6dfa3146a] Validation of action 'InstallVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__HOST,ACTION_TYPE_FAILED_PROVIDER_TYPE_MISMATCH - If for example we failing to add the host on the first attempt and install failed, let's say cause of some missing package and then we try to re-install it, we blocked. we need to remove it first and then add again. Version-Release number of selected component (if applicable): 4.2.0-0.0.master.20171013142622.git15e767c.el7.centos How reproducible: 100% Steps to Reproduce: 1. Add host to latest master and cause installation to fail cause of some missing package 2. Try to re-install Actual results: Operation Canceled - Error while executing action: silver-vdsb.qa.lab.tlv.redhat.com: Cannot edit Host. The provider type should be 'OpenStack Networking'. Expected results: Should work
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
*** Bug 1503728 has been marked as a duplicate of this bug. ***
*** Bug 1503564 has been marked as a duplicate of this bug. ***
Verified on: 4.2.0-0.0.master.20171027213842.gitded437c.el7.centos
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.