Toshiaki Hatano created CLOUDSTACK-3867:
-------------------------------------------
Summary: [KVM][NPE] System VMs failed to start in advanced zone
with KVM agent, VLAN isolation
Key: CLOUDSTACK-3867
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3867
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: KVM, Management Server
Affects Versions: Future
Environment: master branch: b2cad5b698ff20954bcc36d46dd623e8ca1990c1
Tested with KVM agent, Advanced Zone
Reporter: Toshiaki Hatano
Assignee: Toshiaki Hatano
Priority: Critical
Reproduce procedure:
1. Create advanced zone with VLAN isolation with KVM hypervisor
2. System VMs failed to start
Agent.log:
2013-07-26 17:16:44,068 WARN [cloud.agent.Agent] (agentRequest-Handler-4:null)
Caught:
java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.resource.BridgeVifDriver.plug(BridgeVifDriver.java:118)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3504)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3266)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3291)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1223)
at com.cloud.agent.Agent.processRequest(Agent.java:499)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:807)
at com.cloud.utils.nio.Task.run(Task.java:83)
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)
Root cause:
Management server pass wrongly formatted broadcastUri for public network in
NicTO.
It should be formatted as "vlan://XXXX" but NicTO has "vlan:XXXX".
So VifDrivers (both Bridge, OVS) cannot get vlan id from broadcastUri.
--
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
