ODL : ERROR networking_odl.common.odl_features ConnectionError: HTTPConnectionPool

Bug #1775315 reported by Shivashankar C R
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-odl
New
Undecided
Unassigned
openstack-ansible
Incomplete
Undecided
Manuel Buil

Bug Description

Hi,

I am trying to deploy OSA + ODL with stable/queens(17.0.4) on Ubuntu-16.04.

Followed this link for the installation:
https://docs.openstack.org/openstack-ansible-os_neutron/queens/app-opendaylight.html

As mentioned in that there was already a role present in /etc/ansible/roles for opendaylight.
So i didnt do anything else, changed use_varaibles.yml and run setup_everything.yml.

Have i missed any step here? And i am unable to understand which version of ODL it will install.

I am getting these below errors:

---------------------
2018-06-06 10:17:56.708 8141 ERROR networking_odl.common.odl_features raise ConnectTimeout(e, request=request)
2018-06-06 10:17:56.708 8141 ERROR networking_odl.common.odl_features ConnectTimeout: HTTPConnectionPool(host='192.168.1.50', port=8180): Max retries exceeded with url: /restconf/operational/neutron:neutron/neutron:features/ (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f5259e3ab50>, 'Connection to 192.168.1.50 timed out. (connect timeout=10)'))
2018-06-06 10:17:56.708 8141 ERROR networking_odl.common.odl_features
2018-06-06 10:17:56.709 8141 WARNING networking_odl.common.odl_features [req-cf99b295-e787-450c-a618-ee2d7bc80476 - - - - -] Failed to retrieve ODL features, attempt 367
2018-06-06 10:18:11.728 8141 ERROR networking_odl.common.odl_features [req-cf99b295-e787-450c-a618-ee2d7bc80476 - - - - -] Error connecting to ODL to retrieve features: ConnectTimeout: HTTPConnectionPool(host='192.168.1.50', port=8180): Max retries exceeded with url: /restconf/operational/neutron:neutron/neutron:features/ (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f5259e3a8d0>, 'Connection to 192.168.1.50 timed out. (connect timeout=10)'))
2018-06-06 10:18:11.728 8141 ERROR networking_odl.common.odl_features Traceback (most recent call last):
2018-06-06 10:18:11.728 8141 ERROR networking_odl.common.odl_features File "/openstack/venvs/neutron-17.0.4/lib/python2.7/site-packages/networking_odl/common/odl_features.py", line 93, in _fetch_features
2018-06-06 10:18:11.728 8141 ERROR networking_odl.common.odl_features response = client.request('get')
2018-06-06 10:18:11.728 8141 ERROR networking_odl.common.odl_features File "/openstack/venvs/neutron-17.0.4/lib/python2.7/site-packages/networking_odl/common/client.py", line 91, in request
2018-06-06 10:18:11.728 8141 ERROR networking_odl.common.odl_features method, url=url, headers=headers, data=data, timeout=self.timeout)
2018-06-06 10:18:11.728 8141 ERROR networking_odl.common.odl_features File "/openstack/venvs/neutron-17.0.4/lib/python2.7/site-packages/requests/sessions.py", line 508, in request
2018-06-06 10:18:11.728 8141 ERROR networking_odl.common.odl_features resp = self.send(prep, **send_kwargs)
2018-06-06 10:18:11.728 8141 ERROR networking_odl.common.odl_features File "/openstack/venvs/neutron-17.0.4/lib/python2.7/site-packages/requests/sessions.py", line 618, in send
----------------------------

I would request someone to help if they have faced the same issue.

And is there a way to change the odl_ip to my external_lb_vip_address?? (i dont have GUI version of Ubuntu installed)

odl_ip: "{{ hostvars[groups['opendaylight'][0]]['ansible_default_ipv4']['address'] }}"

Instead of above line can we change it to??

odl_ip: "{{ external_lb_vip_address }}"

Thanks!

no longer affects: odl
tags: added: networking-odl
tags: added: odl
Changed in openstack-ansible:
assignee: nobody → Manuel Buil (mbuil)
Revision history for this message
Manuel Buil (mbuil) wrote :

Does changing it to odl_ip: "{{ external_lb_vip_address }}" make it work?
Can you confirm that ODL is running and the REST API is up?

Manuel Buil (mbuil)
Changed in openstack-ansible:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.