Containerized zaqar websocket config conflicts with its haproxy config

Bug #1751779 reported by Bogdan Dobrelya
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Juan Antonio Osorio Robles

Bug Description

The command 'openstack overcloud node import instackenv.json' fails:

https://logs.rdoproject.org/56/542556/41/openstack-check/gate-tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001-master/Z15abd32e0dd443f691ce562f6b30ccf0/undercloud/home/jenkins/overcloud_prep_images.log.txt.gz#_2018-02-23_12_09_16

for my testing OVB setup ( https://review.openstack.org/#/c/542556/ ) because of this error:

https://logs.rdoproject.org/56/542556/41/openstack-check/gate-tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001-master/Z15abd32e0dd443f691ce562f6b30ccf0/undercloud/var/log/containers/zaqar/zaqar-server.log.txt.gz

The inspected configuration for zaqar(-websocket) containers vs the haproxy container snippet is here https://pastebin.com/3NEDsykw . It seems that zaqar-websocket needs to bind to 192.168.0.1:9000 for the given example configs, yet it binds to a conflicting haproxy non-SSL frontend IP for zaqar.

Changing the bind IP to 192.168.24.1 worked and made the command 'openstack overcloud node import instackenv.json' bypassed the error.

Changed in tripleo:
importance: Undecided → High
milestone: none → queens-rc1
status: New → Triaged
description: updated
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

Comparing undercloud.conf with the generated /etc/hosts, it seems we have the latter borked for undercloud: https://pastebin.com/eYnXKW85 ? Still, I'm not sure how bind IP gets set for the zaqar configs

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (master)

Fix proposed to branch: master
Review: https://review.openstack.org/548035

Changed in tripleo:
assignee: nobody → Juan Antonio Osorio Robles (juan-osorio-robles)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (master)

Reviewed: https://review.openstack.org/548035
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=3ba9190749dbb13a8f7259ee277d22460dd86f59
Submitter: Zuul
Branch: master

commit 3ba9190749dbb13a8f7259ee277d22460dd86f59
Author: Juan Antonio Osorio Robles <email address hidden>
Date: Mon Feb 26 16:21:13 2018 +0200

    Zaqar: Bind to IP, not proxied host

    Zaqar's websocket endpoint is binding to the proxied hostname instead of
    the actual IP that the service should be listening on. This is not
    correct as that interface is used by HAProxy.

    Change-Id: I3e528ef072a8d21984e4d4b05b41de99be5b1d0d
    Closes-Bug: #1751779

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 8.0.0.0rc1

This issue was fixed in the openstack/tripleo-heat-templates 8.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.