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
This commit is contained in:
parent
031fa7ea3e
commit
5fdb4d7913
|
@ -674,6 +674,7 @@ zaqar::keystone::auth_websocket::password: {{UNDERCLOUD_ZAQAR_PASSWORD}}
|
|||
zaqar::server::service_name: 'httpd'
|
||||
zaqar::unreliable: true
|
||||
zaqar::transport::websocket::bind: {{LOCAL_IP}}
|
||||
zaqar::transport::websocket::notification_bind: {{LOCAL_IP}}
|
||||
zaqar::wsgi::apache::bind_host: {{LOCAL_IP}}
|
||||
zaqar::wsgi::apache::ssl: false
|
||||
zaqar::message_store: swift
|
||||
|
|
Loading…
Reference in New Issue