You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "venkata swamybabu budumuru (JIRA)" <ji...@apache.org> on 2013/03/01 17:05:12 UTC
[jira] [Assigned] (CLOUDSTACK-1429) single account is unable to use
same vnet across multiple physical networks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
venkata swamybabu budumuru reassigned CLOUDSTACK-1429:
------------------------------------------------------
Assignee: Marcus Sorensen (was: venkata swamybabu budumuru)
Marcus,
I have submitted the patch and its on review board. Can you review and commit if you are fine with the fix?
Thanks
> single account is unable to use same vnet across multiple physical networks
> ---------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1429
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1429
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Network Controller
> Affects Versions: 4.1.0, 4.2.0
> Environment: Advanced zone :
> physical network 1 : VLANS : 900-905
> physical network 2 : VLANS : 905-909
> Reporter: venkata swamybabu budumuru
> Assignee: Marcus Sorensen
> Priority: Critical
> Labels: regression
> Fix For: 4.1.0, 4.2.0
>
>
> Steps to reproduce :
> (1) Have setup as mentioned in environment details.
> (2) create a Network in physical network1 (id : 200) and deploy a vm (for ex:- network created is using vlan 905 )
> (3) create another network in physical network2 (id : 201) and deploy a vm
> Observations :
> (i) It tried to pick up vlan 905 from physical network 2 (id : 201) and it failed with the following error.
> Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '905-1-3' for key 'i_op_dc_vnet_alloc__vnet__data_center_id__account_id'
> Attaching all the required logs to the bug.
--
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