overcloud heat metadata endpoints are incorrectly set to localhost
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
puppet-heat |
Fix Released
|
Undecided
|
Steven Hardy |
Bug Description
# URL of the Heat metadata server. NOTE: Setting this is only needed if you
# require instances to use a different endpoint than in the keystone catalog
# (string value)
#heat_metadata_
heat_metadata_
# URL of the Heat waitcondition server. (string value)
#heat_waitcondi
heat_waitcondit
# URL of the Heat CloudWatch server. (string value)
#heat_watch_
heat_watch_
This is wrong - they should either be unset (heat will use the heat endpoints from the keystone catalog, which is generally what you want), or set explicitly to point to the heat server, e.g the public endpoint for heat if it's for some reason not the same as the keystone endpoint due to proxying or something.
Changed in heat: | |
status: | New → Triaged |
milestone: | none → ocata-2 |
assignee: | nobody → Steven Hardy (shardy) |
importance: | Undecided → High |
no longer affects: | heat |
tags: | added: newton-backport-potential |
Looks like this is a bug in puppet-heat, which has some bad hardcoded defaults:
# [*heat_ metadata_ server_ url*] 127.0.0. 1:8000' waitcondition_ server_ url*] 127.0.0. 1:8000/ v1/waitconditio n' watch_server_ url*] 127.0.0. 1:8003'
# (optional) URL of the Heat metadata server
# Defaults to 'http://
#
# [*heat_
# (optional) URL of the Heat waitcondition server
# Defaults to 'http://
#
# [*heat_
# (optional) URL of the Heat cloudwatch server
# Defaults to 'http://