Bug 1448808 - Wrong message when re-installing host as HE host
Summary: Wrong message when re-installing host as HE host
Keywords:
Status: CLOSED DUPLICATE of bug 1441431
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.1.2.1
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-08 08:42 UTC by Elad
Modified: 2017-05-17 12:38 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-05-17 12:38:06 UTC
oVirt Team: SLA
Embargoed:

Attachments (Terms of Use)
engine.log (77.12 KB, application/x-gzip)
2017-05-08 08:42 UTC, Elad 		no flags Details
View All

Description Elad 2017-05-08 08:42:57 UTC 
Created attachment 1277043 [details]
engine.log

Description of problem:

Put host in maintenance -> reinstall -> choose HE subtab -> choose deploy -> OK

Got the following error message:

Cannot edit Host. You are using an unmanaged hosted engine VM. Please upgrade the cluster level to 3.6 and wait for the hosted engine storage domain to be properly imported.



The error message in Webadmin is misleading and not relevant. The cluster compatibility level I'm using is 4.1.



The error message in engine.log:

2017-05-08 04:39:31,721-04 WARN  [org.ovirt.engine.core.bll.hostdeploy.InstallVdsCommand] (default task-18) [a1ae054a-555c-4c73-a12b-23e7163124b7] Validation of action 'InstallVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__HOST,ACTION_TYPE_FAILED_UNMANAGED_HOSTED_ENGINE



Version-Release number of selected component (if applicable):
rhevm-4.1.2-0.1.el7.noarch

How reproducible:
100%
Comment 1 Elad 2017-05-08 08:53:58 UTC 
Occurs when trying to re-install host as a hosted engine host before first storage domain creation in the setup (so the HE storage domain hasn't been imported yet).
Comment 2 Yaniv Lavi 2017-05-17 12:38:06 UTC 

*** This bug has been marked as a duplicate of bug 1441431 ***
Note You need to log in before you can comment on or make changes to this bug.