Zaqar subscriptions failed to report deployment error

Bug #1727406 reported by Thomas Herve on 2017-10-25
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
tripleo
Critical
Thomas Herve

Bug Description

Seen on this ci run, still trying to understand what's going on: http://logs.openstack.org/01/513701/3/gate/legacy-tripleo-ci-centos-7-scenario004-multinode-oooq/d5013a0/

We can see the error here: http://logs.openstack.org/01/513701/3/gate/legacy-tripleo-ci-centos-7-scenario004-multinode-oooq/d5013a0/logs/undercloud/var/log/zaqar/zaqar.log.txt.gz#_2017-10-25_09_31_07_869

Failed to establish a new connection: [Errno 111] Connection refused',)).: ConnectionError: HTTPConnectionPool(host='centos-7-vexxhost-ca-ymq-1-0000443726', port=35533): Max retries exceeded with url: /44c18acd-a129-4933-b60e-7402bd25e598

I wonder if it may be a IPv6 misbehavior.

Changed in tripleo:
status: New → Triaged
importance: Undecided → Critical
milestone: none → queens-2
tags: added: ci
Changed in tripleo:
assignee: nobody → Thomas Herve (therve)

Reviewed: https://review.openstack.org/515123
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=5fdb4d7913bfc0096c725f6f99fd98e949c75d58
Submitter: Zuul
Branch: master

commit 5fdb4d7913bfc0096c725f6f99fd98e949c75d58
Author: Thomas Herve <email address hidden>
Date: Wed Oct 25 18:17:06 2017 +0200

    Set notification_bind on zaqar websocket

    Don't let zaqar websocket listen to notifications on all interfaces:
    otherwise, it uses the hostname as a subscription target, and it doesn't
    work when the host is set as an IPv6 host. Ultimately this should be
    fixed in Zaqar, but this will work around it for now.

    Change-Id: I78e0671024b93ec64740cd7a8cda227a5145b789
    Related-Bug: #1727406

Reviewed: https://review.openstack.org/515290
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=211eb5bc6c4a019e0b70c99697cc66614f68c1d1
Submitter: Zuul
Branch: stable/pike

commit 211eb5bc6c4a019e0b70c99697cc66614f68c1d1
Author: Thomas Herve <email address hidden>
Date: Wed Oct 25 18:17:06 2017 +0200

    Set notification_bind on zaqar websocket

    Don't let zaqar websocket listen to notifications on all interfaces:
    otherwise, it uses the hostname as a subscription target, and it doesn't
    work when the host is set as an IPv6 host. Ultimately this should be
    fixed in Zaqar, but this will work around it for now.

    Change-Id: I78e0671024b93ec64740cd7a8cda227a5145b789
    Related-Bug: #1727406
    (cherry picked from commit 5fdb4d7913bfc0096c725f6f99fd98e949c75d58)

tags: added: in-stable-pike
Thomas Herve (therve) on 2017-11-06
summary: - Zaqar subcriptions failed to report deployment error
+ Zaqar subscriptions failed to report deployment error
Martin André (mandre) wrote :

Removing the alert tag, https://review.openstack.org/#/c/517889/ was merged in both master and stable/pike.

tags: removed: alert

Reviewed: https://review.openstack.org/516983
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=41a319490178c5bb72d7559ea211c013984f0ae8
Submitter: Zuul
Branch: master

commit 41a319490178c5bb72d7559ea211c013984f0ae8
Author: Dan Prince <email address hidden>
Date: Wed Nov 1 08:49:01 2017 -0400

    Set notification_bind on zaqar websocket

    Don't let zaqar websocket listen to notifications on all interfaces:
    otherwise, it uses the hostname as a subscription target, and it doesn't
    work when the host is set as an IPv6 host. Ultimately this should be
    fixed in Zaqar, but this will work around it for now.

    Change-Id: Ib7ece313371660ea02bef314bf5b5d2c4121a884
    Related-Bug: #1727406

Changed in tripleo:
status: Triaged → Fix Committed
Changed in tripleo:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers