You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 27, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: