Bug 982139 - [INSTALL]: unclear error message while removing host in up state
Summary: [INSTALL]: unclear error message while removing host in up state
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-setup
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.3.0
Assignee: Ofer Schreiber
QA Contact: Pavel Stehlik
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-08 08:56 UTC by Barak Dagan
Modified: 2015-09-22 13:09 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-09 07:16:37 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Barak Dagan 2013-07-08 08:56:17 UTC 
Description of problem:
[RHEVM shell (connected)]# list hosts --show-all | egrep -w 'id|status'
id                                : c7f4445e-870e-4485-a72d-32217149adb2
status-state                      : up


[RHEVM shell (connected)]# remove host c7f4445e-870e-4485-a72d-32217149adb2

error: 
status: 409
reason: Conflict
detail: var  action  remove, var  type  host, vds cannot remove vds status illegal


Version-Release number of selected component (if applicable):
is4

How reproducible:
100%

Steps to Reproduce:
1. remove host in up state
2.
3.

Actual results:


Expected results:
error: 
status: 409
reason: illegal status
detail: vds is not in maintenance state


Additional info:
Comment 1 Michael Pasternak 2013-07-08 09:16:39 UTC 
this issue is caused due to misplaced AppErros file.
Comment 2 Itamar Heim 2013-08-22 09:40:10 UTC 
is this still relevant?
Comment 3 Barak Dagan 2013-09-09 07:16:37 UTC 
is13 - 

[RHEVM shell (connected.161.51)]# remove host 5ed5c63e-6037-477c-8350-c1dd851a9af4

error: 
status: 409
reason: Conflict
detail: Cannot remove Host. Host is operational. Please switch Host to Maintenance mode first.
Note You need to log in before you can comment on or make changes to this bug.