Knife rackspace plugin


#1

Hi trying to use the rackspace plugin, getting the error below - any
ideas? If there issue with the plugin not matching the current API
that anyone knows of?

I have checked my username and regenerated the key.

$ knife rackspace image list
ERROR: Excon::Errors::Unauthorized: Expected(204) <=> Actual(401 Unauthorized)
request => {:path=>"/v1.0", :scheme=>“https”,
:headers=>{“X-Auth-User”=>"", “Content-Length”=>0,
“X-Auth-Key”=>"", “Host”=>“auth.api.rackspacecloud.com:443”},
:host=>“auth.api.rackspacecloud.com”, :port=>“443”, :method=>“GET”,
:mock=>nil, :expects=>204, :query=>nil}
response => #<Excon::Response:0x1029ee708 @status=401,
@headers={“Date”=>“Tue, 20 Mar 2012 00:59:27 GMT”,
“Content-Type”=>“application/octet-stream”, “Content-Length”=>“24”,
“Server”=>“Apache/2.2.3 (Red Hat)”,
“vary”=>“X-Auth-Token,X-Auth-Key,X-Storage-User,X-Storage-Pass”,
“Connection”=>“Keep-Alive”}, @body=“Bad username or password”>

Thanks,

Kimball Johnson


#2

This is completely anecdotal, but my Rackspace creds stopped working a
few weeks ago and I had to recreate my user and password. I believe it
was the same error. New credentials and it started working again.

Thanks,
Matt Ray
Senior Technical Evangelist | Opscode Inc.
matt@opscode.com | (512) 731-2218
Twitter, IRC, GitHub: mattray

On Mon, Mar 19, 2012 at 8:10 PM, Kimball Johnson kimball@bowerham.net wrote:

Hi trying to use the rackspace plugin, getting the error below - any
ideas? If there issue with the plugin not matching the current API
that anyone knows of?

I have checked my username and regenerated the key.

$ knife rackspace image list
ERROR: Excon::Errors::Unauthorized: Expected(204) <=> Actual(401 Unauthorized)
request => {:path=>"/v1.0", :scheme=>“https”,
:headers=>{“X-Auth-User”=>"", “Content-Length”=>0,
“X-Auth-Key”=>"", “Host”=>“auth.api.rackspacecloud.com:443”},
:host=>“auth.api.rackspacecloud.com”, :port=>“443”, :method=>“GET”,
:mock=>nil, :expects=>204, :query=>nil}
response => #<Excon::Response:0x1029ee708 @status=401,
@headers={“Date”=>“Tue, 20 Mar 2012 00:59:27 GMT”,
“Content-Type”=>“application/octet-stream”, “Content-Length”=>“24”,
“Server”=>“Apache/2.2.3 (Red Hat)”,
“vary”=>“X-Auth-Token,X-Auth-Key,X-Storage-User,X-Storage-Pass”,
“Connection”=>“Keep-Alive”}, @body=“Bad username or password”>

Thanks,

Kimball Johnson


#3

I also had to reset and regenerate the rackspace API token

Ryan

On Monday, March 19, 2012 at 11:25 PM, Matt Ray wrote:

This is completely anecdotal, but my Rackspace creds stopped working a
few weeks ago and I had to recreate my user and password. I believe it
was the same error. New credentials and it started working again.

Thanks,
Matt Ray
Senior Technical Evangelist | Opscode Inc.
matt@opscode.com | (512) 731-2218
Twitter, IRC, GitHub: mattray

On Mon, Mar 19, 2012 at 8:10 PM, Kimball Johnson kimball@bowerham.net wrote:

Hi trying to use the rackspace plugin, getting the error below - any
ideas? If there issue with the plugin not matching the current API
that anyone knows of?

I have checked my username and regenerated the key.

$ knife rackspace image list
ERROR: Excon::Errors::Unauthorized: Expected(204) <=> Actual(401 Unauthorized)
request => {:path=>"/v1.0", :scheme=>“https”,
:headers=>{“X-Auth-User”=>"", “Content-Length”=>0,
“X-Auth-Key”=>"", “Host”=>“auth.api.rackspacecloud.com:443”},
:host=>“auth.api.rackspacecloud.com”, :port=>“443”, :method=>“GET”,
:mock=>nil, :expects=>204, :query=>nil}
response => #<Excon::Response:0x1029ee708 @status=401,
@headers={“Date”=>“Tue, 20 Mar 2012 00:59:27 GMT”,
“Content-Type”=>“application/octet-stream”, “Content-Length”=>“24”,
“Server”=>“Apache/2.2.3 (Red Hat)”,
“vary”=>“X-Auth-Token,X-Auth-Key,X-Storage-User,X-Storage-Pass”,
“Connection”=>“Keep-Alive”}, @body=“Bad username or password”>

Thanks,

Kimball Johnson


#4

On Mar 20, 2012, at 4:25 AM, Matt Ray wrote:

This is completely anecdotal, but my Rackspace creds stopped working a
few weeks ago and I had to recreate my user and password. I believe it
was the same error. New credentials and it started working again.

The credentials for my “justenoughchef” account are brand new, so unfortunately this is not the problem I’ve been having. The problem I’ve been seeing is shown at https://gist.github.com/de448b0867e604d6efb2/1621c21a6e4c2a1df1039625a4f01d49600b902a.


Brad Knowles bknowles@ihiji.com
SAGE Level IV, Chef Level 0.0.1


#5

On 20 March 2012 07:06, Brad Knowles bknowles@ihiji.com wrote:

On Mar 20, 2012, at 4:25 AM, Matt Ray wrote:

This is completely anecdotal, but my Rackspace creds stopped working a
few weeks ago and I had to recreate my user and password. I believe it
was the same error. New credentials and it started working again.

The credentials for my “justenoughchef” account are brand new, so unfortunately this is not the problem I’ve been having. The problem I’ve been seeing is shown at https://gist.github.com/de448b0867e604d6efb2/1621c21a6e4c2a1df1039625a4f01d49600b902a.

Well it turns out my issue was my rackspace is london based so has a
different authentication server.

Brad’s issue - if you make -flavour 1 --flavour 1 then it works

Kimball


#6

Well it turns out my issue was my rackspace is london based so has a
different authentication server.

Brad’s issue - if you make -flavour 1 --flavour 1 then it works

Still finding after this that it tries to access a dns name for the
instance, but this doesn’t seem to exist when knife tries to ssh in.

Is there are way to get it to use the IP address instead.

Kimball