Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Sat, 6 Apr 2013 01:21:16 +0000 (UTC)
From: "Sangeetha Hariharan (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12640425.1364955307845.120639.1365211276357@arcas>
In-Reply-To: <JIRA.12640425.1364955307845@arcas>
References: <JIRA.12640425.1364955307845@arcas>
Subject: [jira] [Closed] (CLOUDSTACK-1900) Upgrade 4.0 -> 4.1 , We do not
 have a copy of db.properties that comes from a 4.1 installation saved
 anywhere.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sangeetha Hariharan closed CLOUDSTACK-1900.
-------------------------------------------


Tested with latest build from 4.1:

When upgrading from 4.0 -> 4.1 , we preserve the old db.properties from 4.0 installation to the /etc/cloudstack/management directory as db.properties.
 4.1 db.properties gets saved as db.properties.rpmnew.

Closing this issue
                
> Upgrade 4.0 -> 4.1 , We do not have a copy of db.properties that comes from a 4.1 installation saved anywhere.
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1900
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1900
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.1.0
>         Environment: Upgrade from 4.0 -> 4.1
>            Reporter: Sangeetha Hariharan
>            Assignee: Marcus Sorensen
>             Fix For: 4.1.0
>
>
> When we upgrade from 4.0 to 4.1 , we do not have a copy of db.properties that comes from a 4.1 installation saved anywhere. 
> This needs to be saved , So that as part of upgrade instructions we can ask that the user makes his current  db.properties compatible with this version. This step is documented as part of upgrade procedures from 2.2.14-> 4.0 and 3.0.2->4.0.
> I see the following awsapi missing in db.properties when upgrading from 4.0 -> 4.1
>  db.awsapi.username=cloud
> db.awsapi.password=cloud
> db.awsapi.host=localhost
> db.awsapi.port=3306

--
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