Newton: oslo.messaging Bad address when CONFIG_AMQP_ENABLE_SSL=y

Bug #1675804 reported by Grelaud on 2017-03-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Andy McCrae

Bug Description

Newton 14.1.1

ERROR oslo_messaging.notify.listener File "/usr/lib/python2.7/", line 272, in write
ERROR oslo_messaging.notify.listener return self._sslobj.write(data)
ERROR oslo_messaging.notify.listener error: [Errno 14] Bad address

See bug report:

version of oslo.messaging in newton: oslo.messaging-5.10.1

It seems that is solved in version 5.18 and in ocata.

I patched (/openstack/venvs/ceilometer-14.1.1/lib/python2.7/site-packages/oslo_messaging/_drivers/ and no more Bad address for me.

Ceilometer-collector is now functionnal.

Grelaud (fabrice-grelaud) wrote :
Changed in openstack-ansible:
assignee: nobody → Andy McCrae (andrew-mccrae)
Andy McCrae (andrew-mccrae) wrote :

In OSA we consume the upper-constraints and requirements from the requirements repository itself (for stable/newton in this case).

That means we'll have to wait for to land and for upper constraints in requirements to change to point to the new version of oslo.messaging.

Once that happens all the OSA roles will consume the newer version of oslo.messaging.

I'm surprised that ocata is working though - since the bump in requirements hasn't moved above 5.17.1 (which doesn't include that fix from what I can tell).

I'll keep this open to track the progress of those changes.

Grelaud (fabrice-grelaud) wrote :

I understand we have to wait for newton. Notice this issue only on my ceilometer-collector service. So i just patched for that service only. Don't want to break my OSA environment.
Ceilometer can work now.

For ocata, seems ok:


Changed in openstack-ansible:
importance: Undecided → Medium
status: New → In Progress
Andy McCrae (andrew-mccrae) wrote :

Following up on old bugs - since this merged (ages ago) Closing this as fix released.

Changed in openstack-ansible:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers