Bug 1303518

Summary: After restart of the opendaylight service networks list is empty
Product: Red Hat OpenStack Reporter: Itzik Brown <itbrown>
Component: opendaylightAssignee: lpeer <lpeer>
Status: CLOSED DUPLICATE QA Contact: Toni Freger <tfreger>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.0 (Liberty)CC: mkolesni, nyechiel
Target Milestone: ---   
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-04 13:51:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Itzik Brown 2016-02-01 07:50:12 UTC 
Description of problem:
After restarting opendaylight service and running the following:

curl -H "Content-Type:application/json" -u admin:admin http://127.0.0.1:8080/controller/nb/v2/neutron/networks

The output is:
{
   "networks" : [ ]
}

Even though the networks exist on Neutron.
After creating another network the above command shows all the networks.

Version-Release number of selected component (if applicable):
opendaylight-0.1.1-4.el7ost.noarch
python-networking-odl-1.0.1-1.el7ost.noarch
python-neutron-7.0.0-5.el7ost.noarch
openstack-neutron-7.0.0-5.el7ost.noarch
openstack-neutron-ml2-7.0.0-5.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create a network
2. Verify that you can see the network when querying the ODL controller
   # curl -H "Content-Type:application/json" -u admin:admin http://<ODL controller IP>:8080/controller/nb/v2/neutron/networks
3. Restart the ODL controller
4. Verify output of the command in #2 shows no network 

Actual results:


Expected results:


Additional info:
Comment 2 Nir Yechiel 2016-02-04 13:51:48 UTC 

*** This bug has been marked as a duplicate of bug 1303520 ***