Bug 1457338 - Zaqar messages cannot be enqueued
Summary: Zaqar messages cannot be enqueued
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-zaqar
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
Target Milestone: Upstream M3
: 12.0 (Pike)
Assignee: RHOS Maint
QA Contact: Udi Kalifon
Depends On:
TreeView+ depends on / blocked
Reported: 2017-05-31 14:18 UTC by Jason E. Rist
Modified: 2018-02-05 19:07 UTC (History)
13 users (show)

Fixed In Version: openstack-zaqar-5.0.0-0.20170719124338.13b85cc.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-13 21:29:42 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 1693862 0 None None None 2017-05-31 14:18:36 UTC
OpenStack gerrit 470964 0 None None None 2017-06-07 14:00:19 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Jason E. Rist 2017-05-31 14:18:33 UTC
Cloned from launchpad bug 1693862.


Messages cannot be sent to the "tripleo" queue via the Zaqar websocket connection.  After a fresh undercloud install, everything works fine but after some time, messages start to get refused.

Running the script below, here is the error that is returned:

{u'body': {u'message': u'Authentified.'}, u'headers': {u'status': 200}, u'request': {u'action': u'authenticate', u'body': {}, u'api': u'v2', u'headers': {}}}

{u'body': {u'exception': u'Object GET failed: 404 Not Found  [first 60 chars of response] <html><h1>Not Found</h1><p>The resource could not be found.<', u'error': u'Unexpected error.'}, u'headers': {u'status': 500}, u'request': {u'action': u'message_post', u'body': {u'queue_name': u'tripleo', u'messages': [{u'body': {u'timestamp': u'1495805427754', u'message': u'ohai', u'level': u'INFO'}, u'ttl': 300}]}, u'api': u'v2', u'headers': {u'Client-ID': u'4ad8df3d-e13b-4b8c-8fc9-8204207bea40', u'X-Project-ID': u'ce2db07affc44072a1054214305a4b93'}}}

In the first line, you can see that the client is successfully authenticated to the service.  In the second line, you can see that there is an error coming through via Swift.

There is nothing at all about this in /var/log/zaqar/zaqar.log or /var/log/swift.

This has been happening for a while now (weeks?).

Environment: latest undercloud built from master

You can use this quick Python script (that I received from someone on IRC) to enqueue messages via Zaqar's websocket endpoint:

    import websocket
    import uuid
    import json

    project = ""
    token = ""

    client_id = str(uuid.uuid4())

    ws = websocket.create_connection('ws://')
        'action': 'authenticate',
        'headers': {
            'X-Auth-Token': token,
            'Client-ID': client_id,
            'X-Project-ID': project
    data = json.loads(ws.recv())
    print data

        "action": "message_post",
        "headers": {
            "Client-ID": client_id,
            "X-Project-ID": project
        "body": {
            "messages": [{
                "body": "Hello",
                "ttl": 300
            "queue_name": "tripleo"

    data = json.loads(ws.recv())
    print data

Specification URL (additional information):


Comment 4 Dan Trainor 2017-11-06 15:51:29 UTC
Messages are enqueued and can be picked up using this test script which mimics a request.

This happens in at least:


Comment 7 errata-xmlrpc 2017-12-13 21:29:42 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.