Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Fri, 24 Jul 2015 09:30:04 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12845891.1437142354000.279724.1437730204828@Atlassian.JIRA>
In-Reply-To: <JIRA.12845891.1437142354000@Atlassian.JIRA>
References: <JIRA.12845891.1437142354000@Atlassian.JIRA>
 <JIRA.12845891.1437142354252@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-8649) Register SSH keypair is broken
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Commit 8dc8e9b8f31ef249a553cb20fb5be617a74cfbba in cloudstack's branch refs/heads/4.5 from [~boris@pcextreme.nl]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8dc8e9b ]

CLOUDSTACK-8649: Fixed unnecessary double url decoding in registerSSHKeyPair.

Signed-off-by: wilderrodrigues <wrodrigues@schubergphilis.com>

This closes #615

(cherry picked from commit 2e79c628e052ebdaf782458cfe4c4ef6e95545c6)
Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>

Conflicts:
	server/src/com/cloud/server/ManagementServerImpl.java


> Register SSH keypair is broken
> ------------------------------
>
>                 Key: CLOUDSTACK-8649
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8649
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.5.0, 4.5.1
>            Reporter: Lennert den Teuling
>
> It seems that when we upgraded form CS 4.3 to 4.5 the register SSH keypair functionality broke. 
> Registering keypairs work, but deployments with these newly registered keypair fails because they are not correctly put into the database. 
> It seems that at least half of the public key data is missing in the database. We have tried this with multiple keys, even with keys that worked before. Keys that were registered before the upgrade still work. 
> It is simple to reproduce, just register a SSH key and you will see the key will to be correctly put into the "ssh_keypairs" table and encrypting the VM password with the key will fail on deployment. 


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