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
Maybe this was fixed after 0.0.2; I'm afraid I can't easily check that at the moment.
I got this error:
no implicit conversion of String into Hash
/Users/henrik/.rvm/gems/ruby-2.1.0@barsoom_servers/gems/rest-client-1.6.7/lib/restclient/resource.rb:50:in `merge'
/Users/henrik/.rvm/gems/ruby-2.1.0@barsoom_servers/gems/rest-client-1.6.7/lib/restclient/resource.rb:50:in `get'
/Users/henrik/.rvm/gems/ruby-2.1.0@barsoom_servers/gems/proxmox-0.0.2/lib/proxmox.rb:346:in `http_action_get'
/Users/henrik/.rvm/gems/ruby-2.1.0@barsoom_servers/gems/proxmox-0.0.2/lib/proxmox.rb:137:in `openvz_get'
Basically the issue seems to be that create_ticket does @connection_status = "error" as the last thing in the error branch, meaning it returns the "error" string.
The Proxmox::Proxmox initializer sets @auth_params = create_ticket.
http_action_get does @site[url].get @auth_params … where @auth_params will be the "error" string instead of a hash, causing that confusing error message.
Would be nice if the message was clearer about the actual issue.
The text was updated successfully, but these errors were encountered:
@Walter900 I think the issue I reported was just that you would get an incorrect error message when you couldn't authenticate (e.g. if you have the wrong password). So the fix for me was to use the right password. And I encouraged the proxmox project to clarify the error message.
Maybe this was fixed after 0.0.2; I'm afraid I can't easily check that at the moment.
I got this error:
Basically the issue seems to be that
create_ticket
does@connection_status = "error"
as the last thing in the error branch, meaning it returns the"error"
string.The
Proxmox::Proxmox
initializer sets@auth_params = create_ticket
.http_action_get
does@site[url].get @auth_params …
where@auth_params
will be the"error"
string instead of a hash, causing that confusing error message.Would be nice if the message was clearer about the actual issue.
The text was updated successfully, but these errors were encountered: