[
https://issues.apache.org/jira/browse/CLOUDSTACK-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeetha Hariharan updated CLOUDSTACK-1710:
--------------------------------------------
Summary: AWS Regions - As part of adding a new region,default_zone_id
column for the account entries should not be synced. (was: Regions - As part
of adding a new region,default_zone_id column for the account entries should
not be synced.)
> AWS Regions - As part of adding a new region,default_zone_id column for the
> account entries should not be synced.
> -----------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1710
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1710
> 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: Build from 4.1.0
> Reporter: Sangeetha Hariharan
> Assignee: Kishan Kavala
> Fix For: 4.1.0
>
>
> Regions - As part of adding a new region,default_zone_id column for the
> account entries should not be synced..
> FS states the following needs to be done when adding a new region.
> mysqldump -u cloud -p -h <region1_db_host> cloud account user domain >
> region1.sql
> mysql -u cloud -p -h <regionN_db_host> cloud < region1.sql
> If accounts have default_zone assigned using markDefaultZoneForAccount() in
> the 1 st region , this default_zone shouls NOT be synced to the new region.
--
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
