[NEUTRON-155] neutron models are not popluated Created: 23/Jan/18 Updated: 29/Jan/18 Resolved: 29/Jan/18 |
|
| Status: | Resolved |
| Project: | neutron |
| Component/s: | transcriber |
| Affects Version/s: | master |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Highest |
| Reporter: | Sam Hague | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
in the job below which is using the latest integration/test distribution with the bump patches, we are not seeing any of the neutron models being populated. We see ovsdb and ovs events but nothing from the neutron side. In the networking-odl logs we see communication failures to ODL
2018-01-22 21:39:30.250 9169 ERROR networking_odl.common.client [-] REST request ( post ) to url ( security-groups ) is failed.Request body : [{u'security_group': {'id': 'a2af6801-ce36-4d6d-982f-438334664575', 'tenant_id': u'2dd7cb5908b94f718093103812583a2c', 'project_id': u'2dd7cb5908b94f718093103812583a2c', 'description': u'Default security group', 'name': 'default'}}] service 2018-01-22 21:39:30.250 9169 ERROR networking_odl.journal.journal [-] Cannot connect to the Opendaylight Controller
2018-01-22 21:45:49.714 9169 ERROR networking_odl.common.client [-] REST request ( post ) to url ( networks ) is failed.Request body : [{u'network': {'availability_zone_hints': '[]', 'name': u'l2_net_1', 'provider:physical_network': u'physnet1', 'admin_state_up': True, 'tenant_id': u'88db0c9902f0410c9fc9da41fffcf199', 'mtu': 1400, 'router:external': False, 'provider:network_type': u'vlan', 'port_security_enabled': True, 'shared': False, 'project_id': u'88db0c9902f0410c9fc9da41fffcf199', 'id': '02872d30-d4e5-48d5-b69c-d22551415592', 'provider:segmentation_id': 1121}}] service 2018-01-22 21:45:49.715 9169 ERROR networking_odl.journal.journal [-] Cannot connect to the Opendaylight Controller
|
| Comments |
| Comment by Sam Hague [ 23/Jan/18 ] |
|
Looks like maybe the http ports are different now. In working jobs before the parent bump it looks like ports 8080 and 8181 were both opened. networking-odl used 8080 by default. That is shown in the first link below. In the second, the failing jobs, only port 8181 is opened 2018-01-13 03:50:26,910 | INFO | onfig-1-thread-1 | JettyServerImpl | 419 - org.ops4j.pax.web.pax-web-jetty - 4.3.4 | Pax Web available at [0.0.0.0]:[8181] 2018-01-13 03:50:26,910 | INFO | onfig-1-thread-1 | JettyServerImpl | 419 - org.ops4j.pax.web.pax-web-jetty - 4.3.4 | Pax Web available at [0.0.0.0]:[8080] 2018-01-22T21:00:58,891 | INFO | Blueprint Extender: 3 | AbstractConnector | 176 - org.eclipse.jetty.util - 9.3.15.v20161220 | Started jetty-default@49f0c3bc{HTTP/1.1,[http/1.1]}{0.0.0.0:8181}
Here is log in networking-odl showing it is using 8080: 2018-01-22 21:39:30.466 9168 DEBUG networking_odl.common.client [-] Sending METHOD (post) URL (http://10.30.170.86:8080/controller/nb/v2/neutron/security-groups) JSON ({
|
| Comment by Sam Hague [ 29/Jan/18 ] |
|
This looks to have been a failure due to the odlparent/yangtools upgrade. More patches have gone in for that effort and the issue seems to have gone away. |