You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Wei Zhou (JIRA)" <ji...@apache.org> on 2013/06/01 16:11:19 UTC
[jira] [Commented] (CLOUDSTACK-1866) NPE while getting VPC Netusage
statistics @ KVM cloud agent
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672114#comment-13672114 ]
Wei Zhou commented on CLOUDSTACK-1866:
--------------------------------------
It looks the parameter of createVPC command is not correct in automation test/
> NPE while getting VPC Netusage statistics @ KVM cloud agent
> ------------------------------------------------------------
>
> Key: CLOUDSTACK-1866
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1866
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server, Network Controller
> Affects Versions: 4.1.0
> Reporter: Sailaja Mada
> Assignee: Kishan Kavala
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: agent.log, apilog.log, management-server.log
>
>
> Setup:
> MS : Rhel 6.3 with KVM 6.3 host , Advanced Networking
> Steps:
> 1. Stop Management Server and Agent
> 2. Upgrade the packages of MS and Agent from 4.0 to 4.1
> 3. Create VPC with no tiers in it.
> Observation @ Cloud agent log: NPE while getting VPC Netusage statistics @ KVM cloud agent
> 2013-04-01 12:25:52,938 INFO [cloud.agent.Agent] (agentRequest-Handler-2:null) Ready command is processed: agent id = 1
> 2013-04-01 12:59:21,517 INFO [kvm.resource.BridgeVifDriver] (agentRequest-Handler-3:null) Using old style bridge name for vlan 814 because existing bridge cloudVirBr814 was found
> 2013-04-01 12:59:21,599 INFO [kvm.resource.BridgeVifDriver] (agentRequest-Handler-3:null) Using old style bridge name for vlan 100 because existing bridge cloudVirBr100 was found
> 2013-04-01 13:00:58,653 INFO [kvm.resource.BridgeVifDriver] (agentRequest-Handler-4:null) Using old style bridge name for vlan 811 because existing bridge cloudVirBr811 was found
> 2013-04-01 13:00:58,729 INFO [kvm.resource.BridgeVifDriver] (agentRequest-Handler-4:null) Using old style bridge name for vlan 100 because existing bridge cloudVirBr100 was found
> 2013-04-01 13:17:05,849 INFO [kvm.resource.BridgeVifDriver] (agentRequest-Handler-2:null) Using old style bridge name for vlan 100 because existing bridge cloudVirBr100 was found
> 2013-04-01 13:26:53,202 INFO [kvm.resource.BridgeVifDriver] (agentRequest-Handler-2:null) Using old style bridge name for vlan 100 because existing bridge cloudVirBr100 was found
> 2013-04-01 13:40:51,665 INFO [kvm.resource.BridgeVifDriver] (agentRequest-Handler-1:null) Using old style bridge name for vlan 100 because existing bridge cloudVirBr100 was found
> 2013-04-01 13:48:39,861 WARN [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-5:null) Exception: /usr/share/cloudstack-common/scripts/network/domr/router_proxy.sh vpc_netusage.sh 169.254.1.225 -l null -c -v null
> java.lang.NullPointerException
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:457)
> at com.cloud.utils.script.Script.execute(Script.java:183)
> at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.VPCNetworkUsage(LibvirtComputingResource.java:2741)
> at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2766)
> at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1123)
> at com.cloud.agent.Agent.processRequest(Agent.java:525)
> at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
> at com.cloud.utils.nio.Task.run(Task.java:83)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-04-01 13:48:39,904 INFO [kvm.resource.BridgeVifDriver] (agentRequest-Handler-5:null) Using old style bridge name for vlan 100 because existing bridge cloudVirBr100 was found
--
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