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

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

Commit b86b1d925055e36c79b75f63b8c1e611db94fd15 in branch refs/heads/4.1 from 
Chip Childers <[email protected]>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b86b1d9 ]

CLOUDSTACK-1900 : Save a default db.properties during upgrade, and make sure
we only pull the old configs once.

Signed-off-by: Marcus Sorensen <[email protected]> 1364966964 -0600

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

Reply via email to