Bug 924731 - [RHSC-SHELL] Not able to do a force removal of the host from rhsc-shell.
Summary: [RHSC-SHELL] Not able to do a force removal of the host from rhsc-shell.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: 2.1
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Sahina Bose
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-22 11:44 UTC by RamaKasturi
Modified: 2013-04-02 10:05 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-02 10:05:40 UTC
Embargoed:


Attachments (Terms of Use)
Attaching engine,vdsm and glusterfs logs (1.69 MB, application/zip)
2013-03-22 12:44 UTC, RamaKasturi
no flags Details

Description RamaKasturi 2013-03-22 11:44:55 UTC
Description of problem: Not able to do a force removal of the host.


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


How reproducible:

Always


Steps to Reproduce:
1. Login to rhsc-shell by typing the command "rhsc-shell"
2. connect by using the following command "connect --url https://10.70.35.155/api --user admin@internal --password redhat --insecure"
3. add host by using the command "add host --name TestHost1 --address "10.70.35.1" --root_password redhat --cluster-name TestCluster"
4. add volume to that host by using the command "add glustervolume --cluster-identifier TestCluster --name vol1 --volume_type DISTRIBUTE --bricks-brick "brick.server_id=35cfcaa5-1b1e-4be7-b87d-5a018ea98d98,brick.brick_dir=/home/brickInfo/b10" --bricks-brick "brick.server_id=35cfcaa5-1b1e-4be7-b87d-5a018ea98d98,brick.brick_dir=/home/brickInfo/b20"
5. start the volume by using the command "action glustervolume <volname|id> start --cluster-identifier <clusterName|id>"
6. Now move the host to maintenance state by the command "action host <hostname|id> deactivate"
7. Now force remove the host by the command "remove host TestHost1 --force"

  
Actual results:

error: 
status: 400
reason: Bad Request
detail: var  action  remove, var  type  host, vds cannot remove host having gluster volume



Expected results:

It should remove the server and the volumes which has bricks residing on that server.


Additional info:
Force removal of host is happening properly with console.

Comment 2 RamaKasturi 2013-03-22 12:44:58 UTC
Created attachment 714522 [details]
Attaching engine,vdsm and glusterfs logs

Attaching the logs

Comment 3 Sahina Bose 2013-04-02 10:05:40 UTC
The correct syntax is 

remove host TestHost1 --force true

Closing as not a bug since it works with the above command.


Note You need to log in before you can comment on or make changes to this bug.