Heat CFN & Cloudwatch API services are deployed but not configured in haproxy
Bug #1353348 reported by
Simon Pasquier
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Denis Egorenko | ||
5.0.x |
Fix Committed
|
High
|
Denis Egorenko |
Bug Description
Tested in Fuel 5.0/Ubuntu.
The Puppet Heat module installs & configures both the CFN and Cloudwatch API services (respectively listening on port 8000 and 8003) but the HAProxy configuration doesn't include these services.
Either these services shouldn't be installed in the first place or the HAProxy configuration should be updated.
Changed in fuel: | |
importance: | Undecided → Medium |
assignee: | nobody → Fuel Library Team (fuel-library) |
milestone: | none → 6.0 |
Changed in fuel: | |
status: | New → Triaged |
tags: | added: customer-found |
tags: | added: heat |
Changed in fuel: | |
assignee: | Igor Marnat (imarnat) → Denis Egorenko (degorenko) |
importance: | Medium → High |
Changed in fuel: | |
status: | Triaged → In Progress |
Changed in fuel: | |
assignee: | Denis Egorenko (degorenko) → Bogdan Dobrelya (bogdando) |
Changed in fuel: | |
assignee: | Bogdan Dobrelya (bogdando) → Denis Egorenko (degorenko) |
To post a comment you must log in.
I have a customer who is affected by this issue as well. server_ url=http://<public vip>:8000 ion_server_ url=http://<public vip>:8000/ v1/waitconditio n server_ url=http://<public vip>:8003
They try to set up Ceilometer so that additional VMs could be launched automatically by some triggers.
In the heat.conf (heat_api_cfn section) Fuel specifies:
heat_metadata_
heat_waitcondit
heat_watch_
But they all are unusable because they are unavailavle in haproxy.