From 41a319490178c5bb72d7559ea211c013984f0ae8 Mon Sep 17 00:00:00 2001
From: Dan Prince <dprince@redhat.com>
Date: Wed, 1 Nov 2017 08:49:01 -0400
Subject: [PATCH] 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
---
 puppet/services/zaqar-api.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/puppet/services/zaqar-api.yaml b/puppet/services/zaqar-api.yaml
index 7007ce0876..92e36abaa4 100644
--- a/puppet/services/zaqar-api.yaml
+++ b/puppet/services/zaqar-api.yaml
@@ -106,6 +106,7 @@ outputs:
               - {get_param: ZaqarDebug }
             zaqar::server::service_name: 'httpd'
             zaqar::transport::websocket::bind: {get_param: [EndpointMap, ZaqarInternal, host]}
+            zaqar::transport::websocket::notification_bind: {get_param: [EndpointMap, ZaqarInternal, host]}
             zaqar::wsgi::apache::ssl: {get_param: EnableInternalTLS}
             zaqar::wsgi::apache::bind_host: {get_param: [ServiceNetMap, ZaqarApiNetwork]}
             zaqar::message_pipeline: 'zaqar.notification.notifier'