Exit gracefully if reset isn't available for a server.

[aszlig]

This is what's returned when trying to reset a server which doesn't have the option:

{
  "error": {
    "status": 404,
    "code": "RESET_NOT_AVAILABLE",
    "message": "resetting this server is not possible"
  }
}

So let's try to raise a better exception than RobotError

[aszlig]

@cyberplant: What do you get back for the DELL server if you do a GET /reset/IP? Because if just doing a POST on the server is going to be unreliable in return it might be necessary to query it using GET first.

[dangra]

GET /reset/IP returns:

$ curl -sn https://robot-ws.your-server.de/reset/88.xxx.xxx.146 -vv 
* Connected to robot-ws.your-server.de (78.46.1.93) port 443 (#0)
> GET /reset/88.198.113.146 HTTP/1.1
> Authorization: Basic xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> User-Agent: curl/7.36.0
> Host: robot-ws.your-server.de
> Accept: */*
> 
< HTTP/1.1 200 OK
< Date: Thu, 15 May 2014 14:46:53 GMT
* Server Apache is not blacklisted
< Server: Apache
< X-Powered-By: PHP/5.3.28
< Content-Length: 78
< Content-Type: application/json
< 
* Connection #0 to host robot-ws.your-server.de left intact
{"reset":{"server_ip":"88.xxx.xxx.146","server_number":325951,"type":["man"]}}

[dangra]

This is the output for POST /reset/IP

> POST /reset/88.xxx.xxx.146 HTTP/1.1
> Authorization: Basic xxxxxxxxxxxxxxxxxxxx
> User-Agent: curl/7.36.0
> Host: robot-ws.your-server.de
> Accept: */*
> Content-Length: 7
> Content-Type: application/x-www-form-urlencoded
> 

< HTTP/1.1 400 Bad Request
< Date: Thu, 15 May 2014 14:51:19 GMT
< Server: Apache
< X-Powered-By: PHP/5.3.28
< Content-Length: 107
< Connection: close
< Content-Type: application/json
< 
{"error":{"status":400,"code":"INVALID_INPUT","message":"invalid input","missing":null,"invalid":["type"]}}