[
https://issues.apache.org/jira/browse/CLOUDSTACK-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774500#comment-13774500
]
ASF subversion and git services commented on CLOUDSTACK-4704:
-------------------------------------------------------------
Commit 2fa5a5ae97082e4574cf1ae76bfd7e8b0abaff18 in branch refs/heads/master
from [~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2fa5a5a ]
CLOUDSTACK-4704: 41-42 db upgrade - populate vpc_service_map table with the
services/providers supported by VPC
(cherry picked from commit 798f34a49cbfbb3a475f3dadf62d1ac1b8dfa510)
Signed-off-by: Wei Zhou <[email protected]>
> 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.1
>
>
> 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
