[ https://issues.apache.org/jira/browse/CLOUDSTACK-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15842961#comment-15842961 ]
Michael commented on CLOUDSTACK-3783: ------------------------------------- Was this fix? I have the issue in 4.5 and even when trying 4.9 > VPC VR not functioning with Openvswitch > --------------------------------------- > > Key: CLOUDSTACK-3783 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3783 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Network Devices, SystemVM > Affects Versions: 4.1.0, 4.2.0 > Environment: Host: ubuntu 13.04 x86_64 (up-to-date). openvswitch: > 1.9.0. qemu-kvm 1.4.0. libvirt 1.0.2. > Cloudstack configured with advanced networking. Tags for physical networks > - vswitch0 for public & guest traffic > - vif9 for storage traffic > - vif8 for management traffic > Openvswitch configuration: > # ovs-vsctl show > Bridge "vswitch1" > Port "vswitch1" > Interface "vswitch1" > type: internal > Port "eth1" > Interface "eth1" > Port "vif9" > tag: 9 > Interface "vif9" > type: internal > Bridge "vswitch0" > Port "vnet1" > tag: 32 > Interface "vnet1" > Port "vswitch0" > Interface "vswitch0" > type: internal > Port "vif8" > tag: 8 > Interface "vif8" > type: internal > Port "eth0" > Interface "eth0" > Bridge "cloud0" > Port "vnet0" > Interface "vnet0" > Port "cloud0" > Interface "cloud0" > type: internal > ovs_version: "1.9.0" > /etc/cloudstack/agent/agent.properties: > #Storage > #Tue Jul 23 16:57:16 MDT 2013 > guest.network.device=vswitch0 > workers=5 > private.network.device=vif8 > network.bridge.type=openvswitch > port=8250 > resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource > pod=1 > libvirt.vif.driver=com.cloud.hypervisor.kvm.resource.OvsVifDriver > zone=1 > guid=98a9c232-b852-38bb-aec6-9617750429f5 > public.network.device=vswitch0 > cluster=1 > local.storage.uuid=d755f2e8-53ed-40f6-b7bb-923bf3693f09 > domr.scripts.dir=scripts/network/domr/kvm > LibvirtComputingResource.id=1 > Reporter: Dinu Vlad > > When trying to add a VPC, the VR's public interface IP address is not > assigned correctly, nor the source nat or the default route. Cloudstack > reports the VPC is created successfully, however the VR is left in an > "incomplete" state. > Relevant agent.log extract: > 2013-07-19 16:39:20,961 DEBUG [cloud.agent.Agent] > (agentRequest-Handler-2:null) Processing command: > com.cloud.agent.api.PlugNicCommand > 2013-07-19 16:39:20,970 DEBUG [kvm.resource.OvsVifDriver] > (agentRequest-Handler-2:null) plugging nic=[Nic:Public-192.168.1.68-vlan://32] > 2013-07-19 16:39:20,970 DEBUG [kvm.resource.OvsVifDriver] > (agentRequest-Handler-2:null) creating a vlan dev and bridge for public > traffic per traffic label vswitch0 > 2013-07-19 16:39:21,116 DEBUG [cloud.agent.Agent] > (agentRequest-Handler-2:null) Processing command: > com.cloud.agent.api.routing.IpAssocVpcCommand > 2013-07-19 16:39:21,126 DEBUG > [resource.virtualnetwork.VirtualRoutingResource] > (agentRequest-Handler-2:null) Executing: > /usr/share/cloudstack-common/scripts/network/domr/router_proxy.sh > vpc_ipassoc.sh 169.254.2.23 -A -l 192.168.1.68 -c ethnull -g 192.168.1.1 -m > 24 -n 192.168.1.0 > 2013-07-19 16:39:29,107 DEBUG [kvm.resource.LibvirtComputingResource] > (UgentTask-5:null) Executing: > /usr/share/cloudstack-common/scripts/vm/network/security_group.py > get_rule_logs_for_vms > 2013-07-19 16:39:29,233 DEBUG [kvm.resource.LibvirtComputingResource] > (UgentTask-5:null) Execution is successful. > 2013-07-19 16:39:29,235 DEBUG [cloud.agent.Agent] (UgentTask-5:null) Sending > ping: Seq 7-103: { Cmd , MgmtId: -1, via: 7, Ver: v1, Flags: 11, > [{"PingRoutingWithNwGroupsCommand":{"newGroupStates":{},"newStates":{},"_gatewayAccessible":true,"_vnetAccessible":true,"hostType":"Routing","hostId":7,"wait":0}}] > } > 2013-07-19 16:39:29,243 DEBUG [cloud.agent.Agent] (Agent-Handler-5:null) > Received response: Seq 7-103: { Ans: , MgmtId: 112938636298, via: 7, Ver: > v1, Flags: 100010, > [{"PingAnswer":{"_command":{"hostType":"Routing","hostId":7,"wait":0},"result":true,"wait":0}}] > } > 2013-07-19 16:39:38,707 DEBUG > [resource.virtualnetwork.VirtualRoutingResource] > (agentRequest-Handler-2:null) Execution is successful. > 2013-07-19 16:39:38,708 DEBUG > [resource.virtualnetwork.VirtualRoutingResource] > (agentRequest-Handler-2:null) Device "ethnull" does not exist. > Cannot find device "ethnull" > Error: argument "Table_ethnull" is wrong: "table" value is invalid > Error: argument "Table_ethnull" is wrong: "table" value is invalid > RTNETLINK answers: No such process > 2013-07-19 16:39:38,709 DEBUG [cloud.agent.Agent] > (agentRequest-Handler-2:null) Processing command: > com.cloud.agent.api.routing.SetSourceNatCommand > 2013-07-19 16:39:38,719 DEBUG [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-2:null) failing to get physical interface from > bridgecloud0, did not find an eth*, bond*, or vlan* in > /sys/devices/virtual/net/cloud0/brif > 2013-07-19 16:39:38,719 DEBUG [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-2:null) failed to get vlan id from bridge > cloud0attached to physical interface > 2013-07-19 16:39:38,719 DEBUG [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-2:null) failing to get physical interface from > bridgevswitch0, did not find an eth*, bond*, or vlan* in > /sys/devices/virtual/net/vswitch0/brif > 2013-07-19 16:39:38,719 DEBUG [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-2:null) failed to get vlan id from bridge > vswitch0attached to physical interface -- This message was sent by Atlassian JIRA (v6.3.4#6332)