Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Fri, 12 Jul 2013 06:19:48 +0000 (UTC)
From: "Harikrishna Patnala (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12635691.1362615412449.38379.1373609988504@arcas>
In-Reply-To: <JIRA.12635691.1362615412449@arcas>
References: <JIRA.12635691.1362615412449@arcas>
Subject: [jira] [Closed] (CLOUDSTACK-1560) RSA key gets overridden on every
 management server startup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Harikrishna Patnala closed CLOUDSTACK-1560.
-------------------------------------------

    
> RSA key gets overridden on every management server startup
> ----------------------------------------------------------
>
>                 Key: CLOUDSTACK-1560
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1560
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Install and Setup
>    Affects Versions: 4.2.0
>         Environment: OSX 10.8.2
>            Reporter: Alena Prokharchyk
>            Assignee: Harikrishna Patnala
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> aa40c7ee98b36370069effb68388ba751d7dc6e5
> Noticed that the public key in id_rsa.pub file gets overridden on every management server startup. The deployment was done the following way:
> 1) Built - "mvn clean install -P developer,systemvm"
> 2) Deployed the DB - "mvn -P developer -pl developer -Ddeploydb"
> 3) Started management server "mvn -pl :cloud-client-ui jetty:run"
> The ssh key replacement is triggered by step 3).
> I'm running cloudStack on Mac (see OSX version in "Environment" field)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira