[
https://issues.apache.org/jira/browse/CLOUDSTACK-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771577#comment-13771577
]
Alena Prokharchyk commented on CLOUDSTACK-4704:
-----------------------------------------------
For developer to fix:
1) Have to provide the script for customers being on 4.2.1/4.2.0 to fix their
setups. It should be release noted that they have to run it manually.
2) The script should become a part of 4.2.1-4.2.2 upgrade. Although 4.2.1 is
not released yet, but its so close to be shipped, don't think its worth
delaying it by fixging 4.2.0-4.2.1. But please confirm with the community
On CCP (Internal Citrix build) - a part of 4.1 to 4.2 db upgrade path
3) You should handle the situation when customer ran the script manually on
4.2.0, and then upgraded to 4.2.2. In this case you don't have to insert the
records to vpcservicemap table. Basically before inserting the records, do
check if the table already have records for certain vpc. If yes, skip the
upgrade, if no – upgrade.
> DB upgrade bug caused by the new table "vpc_service_map"
> --------------------------------------------------------
>
> Key: CLOUDSTACK-4704
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4704
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.2.0
> Reporter: Alena Prokharchyk
> Assignee: Kishan Kavala
> Priority: Critical
> Fix For: 4.2.0
>
>
> As a part of the commit 836ce6c1, new table vpc_service_map was introduced.
> Before Vpc code used to read services/providers combination from
> vpc_service_offering_map, after the commit it reads from vpc_service_map (the
> way we do for the networks).
> Bug: as a part of the DB upgrade, all existing VPCs are not updated with the
> data in vpc_service_map table. It means existing VPC will never have any
> Services/Providers to implement, and after the existing VR is gone (can
> happen during the VPC restart, or VPC VR removal), it will never gonna get a
> new VR again.
--
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
