cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "venkata swamybabu budumuru (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-3444) [Portable IP] [VPC] Unable to transfer IP between ISOLATED network and VPC Tiered Network
Date Thu, 01 Aug 2013 16:23:53 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

venkata swamybabu budumuru closed CLOUDSTACK-3444.
--------------------------------------------------


Have verified IP transfer from ISOLATED to VPC Tier and vice-versa. It worked fine without
any issue. Closing  this issue.
                
> [Portable IP] [VPC] Unable to transfer IP between ISOLATED network and VPC Tiered Network
> -----------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3444
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3444
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.2.0
>         Environment: commit id # 67cab313c969e5f488d6c0f92f9ec058288a96a0
>            Reporter: venkata swamybabu budumuru
>            Assignee: Murali Reddy
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: logs.tgz
>
>
> Steps to reproduce:
> 1. Have latest CloudStack setup with at least 2 advanced zones (Zone1, Zone2) 
> 2. Create a VPC in one of the zone (Zone2) 
> 3. Create at least 1 Tier in the above created VPC 
> 4. Have at least one ISOLATED network in Zone1
> 5. Acquire at least one portable IP and associate it to the above network created in
step: 4
> 6. enable static NAT on the portable IP acquired in Step:5 to a VM that is running in
Zone2 VPC Tier1
> enable staticnat ipaddressid=4057b22d-f78b-4a34-8548-c745355b01d4 virtualmachineid=9f8ad68a-a8f4-4685-8a38-a4daf4896fce
networkid=921b86ef-4c82-4b49-8bf8-d6f2b93a5963
> HTTP Error 530: 
> Observations:
> (i) It fails with the following error in the management server logs.
> 2013-07-10 12:47:42,468 ERROR [cloud.api.ApiServer] (catalina-exec-7:null) unhandled
exception executing api command: enableStaticNat
> com.cloud.utils.exception.CloudRuntimeException: Unable to find the nic in network 222
 to apply the ip address 10.147.49.224 for
> 	at com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl$1.execute(VpcVirtualNetworkApplianceManagerImpl.java:646)
> 	at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3769)
> 	at com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.associatePublicIP(VpcVirtualNetworkApplianceManagerImpl.java:632)
> 	at com.cloud.network.element.VpcVirtualRouterElement.applyIps(VpcVirtualRouterElement.java:400)
> 	at com.cloud.network.NetworkManagerImpl.applyIpAssociations(NetworkManagerImpl.java:694)
> 	at com.cloud.network.NetworkManagerImpl.applyStaticNats(NetworkManagerImpl.java:3557)
> 	at com.cloud.network.rules.RulesManagerImpl.applyStaticNatForIp(RulesManagerImpl.java:1310)
> 	at com.cloud.network.rules.RulesManagerImpl.enableStaticNat(RulesManagerImpl.java:582)
> 	at com.cloud.network.rules.RulesManagerImpl.enableStaticNat(RulesManagerImpl.java:431)
> 	at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> 	at org.apache.cloudstack.api.command.user.nat.EnableStaticNatCmd.execute(EnableStaticNatCmd.java:129)
> 	at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> 	at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528)
> 	at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)
> 	at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
> 	at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> 	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> 	at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
> 	at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
> 	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 	at java.lang.Thread.run(Thread.java:679)
> 2013-07-10 12:47:42,471 DEBUG [cloud.api.ApiServlet] (catalina-exec-7:null) ===END===
 10.252.192.25 -- GET  apiKey=jryukYWt0W5KBbxnINHcbXdYI1XupuLLoadjkJKqgBWZACHWco9wqsbR1noN7SJfbDh0AsxeGZQbS3PAHBqT3Q&command=enableStaticNat&ipaddressid=4057b22d-f78b-4a34-8548-c745355b01d4&networkid=921b86ef-4c82-4b49-8bf8-d6f2b93a5963&response=json&virtualmachineid=9f8ad68a-a8f4-4685-8a38-a4daf4896fce&signature=fk1Txauo6sU4ki0LNx8%2BdytuSBI%3D
> (ii) I can see that the portable IP assigned to VPC2 Tier1 but, there is no static NAT
rule created on the VPC router.
> (iii) Found that the VPC VR didnt get any eth interface plugged in for the portable IP
VLAN.
> Attaching all the required logs along with db dump 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

Mime
View raw message