Containerized zaqar websocket config conflicts with its haproxy config
Bug #1751779 reported by
Bogdan Dobrelya
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:
for my testing OVB setup ( https:/
The inspected configuration for zaqar(-websocket) containers vs the haproxy container snippet is here https:/
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 |
To post a comment you must log in.
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