You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2013/06/19 20:06:21 UTC
[jira] [Commented] (CLOUDSTACK-558) Duplicate routerVM entry on
network create!
[ https://issues.apache.org/jira/browse/CLOUDSTACK-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688230#comment-13688230 ]
Alena Prokharchyk commented on CLOUDSTACK-558:
----------------------------------------------
The problem is fixed in 4.1/4.2 with commit c36744a18c9a9e64a8b4c92d2ba43f0f644b5f63
> Duplicate routerVM entry on network create!
> -------------------------------------------
>
> Key: CLOUDSTACK-558
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-558
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Environment: 3.0.2->4.0 upgrade, CentOS, VMware
> Reporter: Tamas Monos
> Assignee: Alena Prokharchyk
> Priority: Blocker
>
> Hi,
> In 4.0 when trying to create a new network the "cloud.vm.VirtualMachineManagerImpl" calls the "Allocating entries for VM: VM[DomainRouter|r-x-VM" twice and this causes mysql exception due to the duplicate entry!
> 2012-11-29 13:29:27,511 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-18:job-49) Creating the router 40 in datacenter com.cloud.dc.DataCenterVO$$EnhancerByCGLIB$$88af38d9@1
> 2012-11-29 13:29:27,517 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-18:job-49) Allocating the domR with the hypervisor type VMware
> 2012-11-29 13:29:27,519 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-18:job-49) Allocating entries for VM: VM[DomainRouter|r-40-VM]
> 2012-11-29 13:29:27,523 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-18:job-49) Allocating nics for VM[DomainRouter|r-40-VM]
> 2012-11-29 13:29:27,524 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-18:job-49) Allocating nic for vm VM[DomainRouter|r-40-VM] in network Ntwk[211|Guest|7] with requested profile NicProfile[0-0-null-10.1.1.1-vlan://937
> 2012-11-29 13:29:27,537 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-18:job-49) Service SecurityGroup is not supported in the network id=211
> 2012-11-29 13:29:27,539 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-18:job-49) Allocating nic for vm VM[DomainRouter|r-40-VM] in network Ntwk[202|Control|3] with requested profile null
> 2012-11-29 13:29:27,547 WARN [cloud.network.NetworkManagerImpl] (Job-Executor-18:job-49) Can't get the physical network
> 2012-11-29 13:29:27,548 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-18:job-49) Allocating nic for vm VM[DomainRouter|r-40-VM] in network Ntwk[200|Public|1] with requested profile NicProfile[0-0-null-217.27.254.119-vlan://100
> 2012-11-29 13:29:27,556 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-18:job-49) Allocaing disks for VM[DomainRouter|r-40-VM]
> 2012-11-29 13:29:27,560 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-18:job-49) Allocation completed for VM: VM[DomainRouter|r-40-VM]
> 2012-11-29 13:29:27,560 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-18:job-49) Allocating the domR with the hypervisor type VMware
> 2012-11-29 13:29:27,562 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-18:job-49) Allocating entries for VM: VM[DomainRouter|r-40-VM]
> 2012-11-29 13:29:27,565 DEBUG [db.Transaction.Transaction] (Job-Executor-18:job-49) Rolling back the transaction: Time = 3 Name = -AsyncJobManagerImpl$1.run:398-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRun:334-FutureTask.run:166-ThreadPoolExecutor.runWorker:1110-ThreadPoolExecutor$Worker.run:603-Thread.run:679; called by -Transaction.rollback:887-Transaction.removeUpTo:830-Transaction.close:649-DatabaseCallback.interceptComplete:71-DatabaseCallback.intercept:36-VirtualNetworkApplianceManagerImpl.persist:2476-VirtualNetworkApplianceManagerImpl.persist:235-VirtualMachineManagerImpl.allocate:284-DatabaseCallback.intercept:34-VirtualMachineManagerImpl.allocate:337-VirtualNetworkApplianceManagerImpl.deployRouter:1409-VirtualNetworkApplianceManagerImpl.findOrDeployVirtualRouterInGuestNetwork:1350
> 2012-11-29 13:29:27,567 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-18:job-49) Lock is released for network id 211 as a part of router startup in Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(2)-Storage(Volume(47|ROOT-->Pool(201))]
> 2012-11-29 13:29:27,567 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-18:job-49) Cleaning up because we're unable to implement the network Ntwk[211|Guest|7]
--
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