I ran into this while troubleshooting the ipmi timeout issue that @naved001, brought up: if the HTTP server returns a non-200 status, we raise a FailedAPICallException with the message being the body of the response. In my case, I was getting a 401 with no body, so the command line tool just reported Error:, with nothing after that...
we should make it a bit smarter about good error messages.
I ran into this while troubleshooting the ipmi timeout issue that @naved001, brought up: if the HTTP server returns a non-200 status, we raise a FailedAPICallException with the message being the body of the response. In my case, I was getting a 401 with no body, so the command line tool just reported
Error:
, with nothing after that...we should make it a bit smarter about good error messages.