[OVSDB-80] Integration bridge is not created Created: 11/Sep/14  Updated: 19/Oct/17  Resolved: 23/Sep/14

Status: Resolved
Project: ovsdb
Component/s: openstack.net-virt
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Aryan Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: PC


Issue Links:
Duplicate
duplicates OVSDB-110 ovsdb throws exception, fails to try ... Resolved
External issue ID: 1812

 Description   

General info:

  • devstack
  • distribution.ovsdb-1.2.0-20140909.125353-124-osgipackage.zip

Steps to reproduce:
1- controller$ ./run.sh -virt ovsdb
2- nova boot ...
note: This doesn't happen always

Issues:

  • br-int is not created
  • exceptions in controller

Exception:
2014-09-11 13:48:47.587 CEST [pool-10-thread-1] ERROR o.o.o.o.n.i.ProviderNetworkManagerImpl - No providers matching OpenFlow13 found
2014-09-11 13:48:47.591 CEST [pool-10-thread-1] ERROR o.o.o.o.n.i.BridgeConfigurationManagerImpl - Error creating Integration Bridge on OVS|192.168.10.57:46363
java.util.NoSuchElementException: null
at com.google.common.collect.AbstractIterator.next(AbstractIterator.java:154) ~[bundlefile:na]
at org.opendaylight.ovsdb.openstack.netvirt.impl.ProviderNetworkManagerImpl.getProvider(ProviderNetworkManagerImpl.java:65) ~[bundlefile:na]
at org.opendaylight.ovsdb.openstack.netvirt.impl.BridgeConfigurationManagerImpl.addBridge(BridgeConfigurationManagerImpl.java:654) ~[bundlefile:na]
at org.opendaylight.ovsdb.openstack.netvirt.impl.BridgeConfigurationManagerImpl.createIntegrationBridge(BridgeConfigurationManagerImpl.java:380) ~[bundlefile:na]
at org.opendaylight.ovsdb.openstack.netvirt.impl.BridgeConfigurationManagerImpl.prepareNode(BridgeConfigurationManagerImpl.java:185) ~[bundlefile:na]
at org.opendaylight.ovsdb.openstack.netvirt.SouthboundHandler.processNodeUpdate(SouthboundHandler.java:129) [bundlefile:na]
at org.opendaylight.ovsdb.openstack.netvirt.SouthboundHandler.processEvent(SouthboundHandler.java:351) [bundlefile:na]
at org.opendaylight.ovsdb.openstack.netvirt.impl.EventDispatcherImpl.dispatchEvent(EventDispatcherImpl.java:88) [bundlefile:na]
at org.opendaylight.ovsdb.openstack.netvirt.impl.EventDispatcherImpl.access$100(EventDispatcherImpl.java:28) [bundlefile:na]
at org.opendaylight.ovsdb.openstack.netvirt.impl.EventDispatcherImpl$1.run(EventDispatcherImpl.java:54) [bundlefile:na]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_60]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [na:1.7.0_60]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_60]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_60]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_60]



 Comments   
Comment by Dave Tucker [ 23/Sep/14 ]

Closing this off as the root cause is a timing issue described in 2024

Generated at Wed Feb 07 20:35:27 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.