You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/02/20 20:25:12 UTC
[jira] [Commented] (CLOUDSTACK-1331) Upgrade fails for a 2.2.14
Zone having multiple guest networks using network_tags and Public Vlan
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582446#comment-13582446 ]
ASF subversion and git services commented on CLOUDSTACK-1331:
-------------------------------------------------------------
Commit ec1f48a4b2c31b1f7c3854b0b2ada5322a18e42f in branch refs/heads/master from Prachi Damle <pr...@cloud.com>
[ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=ec1f48a ]
CLOUDSTACK-1331: Upgrade fails for a 2.2.14 Zone having multiple guest networks using network_tags and Public Vlan
Changes:
-We need to update the physical_network_id for public vlans.
-Physical network ID should be retrieved from the network if present.
> Upgrade fails for a 2.2.14 Zone having multiple guest networks using network_tags and Public Vlan
> --------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1331
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1331
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Reporter: Prachi Damle
> Assignee: Prachi Damle
> Fix For: 4.1.0
>
>
> If the Zone has guest network(s) with the tag set (in 2.2.x this info is kept in network_tags table). In this case during the upgrade we miss to update physical_network_id for Public vlans in `cloud`.`vlan` table which results in constraint violation later on causing the upgrade to fail.
> We need to update the physical_network_id for public vlans.
--
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