[
https://issues.apache.org/jira/browse/CLOUDSTACK-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771555#comment-13771555
]
Alena Prokharchyk commented on CLOUDSTACK-4704:
-----------------------------------------------
For QA to test after the fix is in:
1) Create the VPC while being on pre-4.2
2) Upgrade to 4.2
3) Check the following:
* vpc_service_map - VPC should get all the services associated with its
offering, with the VPCVritualRouter provider as a provider
* call restartVPC&id=<vpc id>. As a result, its VPC router should get destroyed
and recreated
> 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
