You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Daan Hoogland (JIRA)" <ji...@apache.org> on 2015/04/23 17:03:38 UTC

[jira] [Commented] (CLOUDSTACK-8400) VPC Private gateway not being removed

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14509179#comment-14509179 ] 

Daan Hoogland commented on CLOUDSTACK-8400:
-------------------------------------------

Do I understand your description correctly if I say that the title is wrong and it is not the VPC private gateway that is not being removed but the vpn gateway?

> VPC Private gateway not being removed
> -------------------------------------
>
>                 Key: CLOUDSTACK-8400
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8400
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Virtual Router
>    Affects Versions: 4.4.2
>         Environment: KVM
>            Reporter: grayson head
>            Assignee: Daan Hoogland
>            Priority: Critical
>
> Unfortunately, I fat fingered a VLAN in a VPC Private gateway I was
> setting up. I removed it using the UI without any errors, but when I
> go to create the new one, I get the following error: "Private network
> for the vlan: vlan://4000 and cidr 10.233.5.0/24 already exists for
> Vpc 16 in zone AusZone1"
> I also tried removing it via cloudmonkey.
> (local) mycloudmonkey> delete privategateway
> id=340b56bb-ee01-49be-84b4-9e54fd2af83d
> .Error
> Async job ed15f016-fd7e-48fb-b92c-0ea07302bffb failed
> Error 530, Invalid private gateway id
> accountid = a9d7423c-a02e-11e4-b7f0-00505695fae7
> cmd = org.apache.cloudstack.api.command.admin.vpc.DeletePrivateGatewayCmd
> created = 2015-04-21T06:38:36-0700
> jobid = ed15f016-fd7e-48fb-b92c-0ea07302bffb
> jobprocstatus = 0
> jobresult:
> errorcode = 530
> errortext = Invalid private gateway id
> jobresultcode = 530
> jobresulttype = object
> jobstatus = 2
> userid = a9d755d8-a02e-11e4-b7f0-00505695fae7
> Looking at the database, the problem becomes somewhat clear:
> mysql> select id,uuid,domain_id,state,removed,ip4_address from vpc_gateways;
> +----+--------------------------------------+-----------+----------+---------------------+--------------+
> | id | uuid                                 | domain_id | state    |
> removed             | ip4_address  |
> +----+--------------------------------------+-----------+----------+---------------------+--------------+
> |  1 | 63a9f6f7-dbe2-4825-a3e2-17e3892c0ded |         1 | Ready    |
> NULL                | 10.233.51.92 |
> |  2 | 340b56bb-ee01-49be-84b4-9e54fd2af83d |         1 | Removing |
> 2015-04-20 21:28:53 | 10.233.5.11  |
> +----+--------------------------------------+-----------+----------+---------------------+--------------+
> 2 rows in set (0.00 sec)
> Unfortunately I don't have the logs from initially removing the VPC. I
> can try and re-create this If needed, but I need to get this
> environment fixed before I do anything else. Will setting the
> state=Removed on the gateway entry in the database correct this?
> Here are the logs from the management-server.log when trying to remove
> the VPC via the UI:
> 2015-04-21 06:36:16,036 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-15:null) SeqA 9-315848: Processing Seq 9-315848:
>  { Cmd , MgmtId: -1, via: 9, Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":78,"_loadInfo":"{\n
>  \"connections\": []\n}","wait":0}}] }
> 2015-04-21 06:36:16,049 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-15:null) SeqA 9-315848: Sending Seq 9-315848:  {
> Ans: , MgmtId: 345050016868, via: 9, Ver: v1, Flags: 100010,
> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}]
> }
> 2015-04-21 06:36:16,853 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-2:null) Ping from 15
> 2015-04-21 06:36:16,877 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-4:null) Ping from 9
> 2015-04-21 06:36:20,715 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-6:ctx-62b2ea0a) ===START===  10.233.51.176 -- GET
> command=createPrivateGateway&sourcenatsupported=false&response=json&sessionkey=sFXaEOKvIpqQArupbqZuPX6wYOo%3D&physicalnetworkid=63a1c53c-b799-452a-ad15-3e0ef582c456&vpcid=0fef5e73-b916-4505-8760-4321a3763bf6&ipaddress=10.233.5.12&gateway=10.233.5.1&netmask=255.255.255.0&vlan=4000&aclid=9599b3fe-a02e-11e4-b7f0-00505695fae7&_=1429623380716
> 2015-04-21 06:36:20,761 DEBUG [c.c.n.v.VpcManagerImpl]
> (catalina-exec-6:ctx-62b2ea0a ctx-ebd9cd79) Creating Private gateway
> for VPC [VPC [16-RSIDevNet]
> 2015-04-21 06:36:20,762 INFO  [c.c.n.v.VpcManagerImpl]
> (catalina-exec-6:ctx-62b2ea0a ctx-ebd9cd79) creating new network for
> vpc [VPC [16-RSIDevNet] using broadcast uri: 4000
> 2015-04-21 06:36:20,774 DEBUG [c.c.n.NetworkServiceImpl]
> (catalina-exec-6:ctx-62b2ea0a ctx-ebd9cd79) Private network already
> exists: Ntwk[2a99ce65-36b0-432e-8fd8-f748a26aabdf|Guest|5]
> 2015-04-21 06:36:20,776 DEBUG [c.c.u.d.T.Transaction]
> (catalina-exec-6:ctx-62b2ea0a ctx-ebd9cd79) Rolling back the
> transaction: Time = 15 Name =  catalina-exec-6; called by
> -TransactionLegacy.rollback:900-TransactionLegacy.removeUpTo:843-TransactionLegacy.close:667-Transaction.execute:41-NetworkServiceImpl.createPrivateNetwork:3991-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:57-DelegatingMethodAccessorImpl.invoke:43-Method.invoke:606-AopUtils.invokeJoinpointUsingReflection:317-ReflectiveMethodInvocation.invokeJoinpoint:183-ReflectiveMethodInvocation.proceed:150
> 2015-04-21 06:36:20,790 INFO  [c.c.a.ApiServer]
> (catalina-exec-6:ctx-62b2ea0a ctx-ebd9cd79) Private network for the
> vlan: vlan://4000 and cidr  10.233.5.0/24  already exists for Vpc 16
> in zone AusZone1
> 2015-04-21 06:36:20,790 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-6:ctx-62b2ea0a ctx-ebd9cd79) ===END===  10.233.51.176
> -- GET  command=createPrivateGateway&sourcenatsupported=false&response=json&sessionkey=sFXaEOKvIpqQArupbqZuPX6wYOo%3D&physicalnetworkid=63a1c53c-b799-452a-ad15-3e0ef582c456&vpcid=0fef5e73-b916-4505-8760-4321a3763bf6&ipaddress=10.233.5.12&gateway=10.233.5.1&netmask=255.255.255.0&vlan=4000&aclid=9599b3fe-a02e-11e4-b7f0-00505695fae7&_=1429623380716
> 2015-04-21 06:36:25,814 DEBUG [c.c.s.StatsCollector]
> (StatsCollector-4:ctx-647080c3) AutoScaling Monitor is running...
> 2015-04-21 06:36:26,037 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-5:null) SeqA 9-315850: Processing Seq 9-315850:
> { Cmd , MgmtId: -1, via: 9, Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":78,"_loadInfo":"{\n
>  \"connections\": []\n}","wait":0}}] }
> 2015-04-21 06:36:26,044 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-5:null) SeqA 9-315850: Sending Seq 9-315850:  {
> Ans: , MgmtId: 345050016868, via: 9, Ver: v1, Flags: 100010,
> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}]
> }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)