Operating System: All
Platform: All

(In reply to Arthi Bhattacharjee from comment #0)
> Procedure to reproduce the bug:
> 1. Download the NetVirt boron distribution.
> 2. Install VPN Service feature.
> feature:install odl-netvirt-openstack
> 3. Stack the control and compute nodes.
>
> NOTE: 10.106.138.153 is control node and 10.106.138.244 is compute node.
>
> 4. Add tunnel configuration.
>
> tep:add 273137343515872 ens34 0 10.106.138.153 10.106.138.0/24 10.106.138.1
> TZA
> tep:add 260070179598380 ens34 0 10.106.138.244 10.106.138.0/24 10.106.138.1
> TZA
>
> 5.Create a network.
> 6. Create a VM in control node and compute node.
> Ping will fail between the VMs.
>
> I tried adding the vxlan manually.
> sudo ovs-vsctl add-port br-int vxlan5 – set interface vxlan5 type=vxlan
> options:remote_ip=10.106.138.244
> Still the ping fails.

Arthi, can you try this again? The autotunnel creation was broken past couple days because of the blueprint changes. Patches below fix the issue.

b: https://git.opendaylight.org/gerrit/43483
c: https://git.opendaylight.org/gerrit/#/c/43551/1

(In reply to Sam Hague from comment #1)
> (In reply to Arthi Bhattacharjee from comment #0)
> > Procedure to reproduce the bug:
> > 1. Download the NetVirt boron distribution.
> > 2. Install VPN Service feature.
> > feature:install odl-netvirt-openstack
> > 3. Stack the control and compute nodes.
> >
> > NOTE: 10.106.138.153 is control node and 10.106.138.244 is compute node.
> >
> > 4. Add tunnel configuration.
> >
> > tep:add 273137343515872 ens34 0 10.106.138.153 10.106.138.0/24 10.106.138.1
> > TZA
> > tep:add 260070179598380 ens34 0 10.106.138.244 10.106.138.0/24 10.106.138.1
> > TZA
> >
> > 5.Create a network.
> > 6. Create a VM in control node and compute node.
> > Ping will fail between the VMs.
> >
> > I tried adding the vxlan manually.
> > sudo ovs-vsctl add-port br-int vxlan5 – set interface vxlan5 type=vxlan
> > options:remote_ip=10.106.138.244
> > Still the ping fails.
>
> Arthi, can you try this again? The autotunnel creation was broken past
> couple days because of the blueprint changes. Patches below fix the issue.
>
> b: https://git.opendaylight.org/gerrit/43483
> c: https://git.opendaylight.org/gerrit/#/c/43551/1

Hi Sam,

While testing with new distro,

https://jenkins.opendaylight.org/releng/view/netvirt/job/netvirt-distribution-boron/165/org.opendaylight.integration$distribution-karaf/artifact/org.opendaylight.integration/distribution-karaf/0.5.0-SNAPSHOT/distribution-karaf-0.5.0-SNAPSHOT.tar.gz

I'm getting the below blueprint error.

2016-08-12 14:19:51,532 | ERROR | rint Extender: 2 | BlueprintContainerImpl | 15 - org.apache.aries.blueprint.core - 1.4.4 | Unable to start blueprint container for bundle org.opendaylight.netvirt.statemanager-impl/0.3.0.SNAPSHOT due to unresolved dependencies [(objectClass=org.opendaylight.netvirt.elanmanager.api.IElanService), (objectClass=org.opendaylight.netvirt.vpnmanager.api.IVpnManager), (objectClass=org.opendaylight.netvirt.neutronvpn.interfaces.INeutronVpnManager)]
java.util.concurrent.TimeoutException
at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:336)[15:org.apache.aries.blueprint.core:1.4.4]
at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)[15:org.apache.aries.blueprint.core:1.4.4]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_92]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_92]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_92]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_92]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_92]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_92]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_92]

Addition to that, while stacking, it is not taking br-int automatically and stack fails.

Arthi,

patches were pushed to fix the elanservice missing dependencies and to fix the auto-bridge creation. Let me know if that work better now.

Thanks, Sam