cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8727) API call listVirtualMachines returns same keypair
Date Wed, 09 Sep 2015 05:10:46 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736186#comment-14736186
] 

ASF subversion and git services commented on CLOUDSTACK-8727:
-------------------------------------------------------------

Commit 76c81a7bd964a01d0fb0180ba101ef90651fab30 in cloudstack's branch refs/heads/master from
[~rajanik]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=76c81a7 ]

Merge pull request #685 from kansal/CLOUDSTACK-8727

CLOUDSTACK-8727: API call listVirtualMachines returns same keypairCurrently the user can register
same key with different names. Upon listing the VM's the name which got registered first is
being returned and not the actual one. Anyhow this behavior is rare and not good. I have added
a UNIQUE constraint on the ssh_keypairs table and also made sure that the previous registered
keys(with duplicates) get deleted.

* pr/685:
  CLOUDSTACK-8727: API call listVirtualMachines returns same keypair: Corrected and test cases
added

Signed-off-by: Rajani Karuturi <rajani.karuturi@citrix.com>


> API call listVirtualMachines returns same keypair
> -------------------------------------------------
>
>                 Key: CLOUDSTACK-8727
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8727
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Kshitij Kansal
>
> If you register 2 SSH keypairs with the same public key then listVirtualMachines API
call will only return the first keypair. Although its a very rare case and generally don't
make much sense by registering the same key with different name, still it can be fixed. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message