cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Robertson <>
Subject Re: Not able to get ssh keypairs listed
Date Thu, 21 Jun 2012 19:15:55 GMT
Hi Jose,

I verified the latest cloudbridge against both 2.2.x CloudStack and 3.0.x
CloudStack and am not duplicating this particular error. Could you verify
you've upgraded your CloudBridge installation to the latest version from

1.1.1 includes a number of changes to deal with ID/UUID changes in
addition to other fixes.

Going forward, CloudBridge has been integrated into the 3.0 branch and
isn't technically supported any longer, however I've been taking patches
and fixing problems when possible.  The 1.1.2 build, which hasn't been
pushed to sourceforge also resolves our REST api authentication problem so
HybridFox and Boto should actually work when it's posted.


On 6/21/12 10:06 AM, "Jose Rozanec" <> wrote:

>Working with cloudbridge we observed the following:* *
>when invoking the listSSHKeyPairs command, cloudbridge fails to list them,
>due to a nullPointerException:
>*POST to Cloudbridge:*
>*Cloudbridge translates this to the following command:*
> Executed:
>*Hits Cloudstack and gets the following response:*
>{ "listsshkeypairsresponse" : { "count":1 ,"sshkeypair" : [
>] } }
>*but then, in the log we observe the following trace:*
>2012-06-21 10:41:04,880 ERROR [core.ec2.EC2Engine] (catalina-exec-9:) EC2
>DescribeKeyPairs -
>        at
>        at
>        at
>Full log trace for the call is provided here
>Are we missing something / is this a known issue?
>Thanks in advance,
>This email and any files transmitted with it are confidential and
>intended solely for the use of the individual or entity to whom they are
>If you have received this email in error please notify the sender.
>Please note that any views or opinions presented in this email are solely
>those of the author and do not necessarily represent those of the company.
>Finally, the recipient should check this email and any attachments for
>the presence of viruses.
>The company accepts no liability for any damage caused by any virus
>transmitted by this email.

View raw message