Heat Software Deployment not working due to incorrect parameter values in heat.conf
Bug #1526886 reported by
Fabio Rauber
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
High
|
Unassigned | ||
7.0.x |
Won't Fix
|
High
|
Registry Administrators | ||
8.0.x |
Invalid
|
Undecided
|
Registry Administrators | ||
Future |
Invalid
|
Undecided
|
Registry Administrators |
Bug Description
Heat Software Deployment is not working in a Kilo environment installed via Openstack Fuel 7.0 (ubuntu 14.04). After a lot of searching, I found out that various parameters in heat.conf are pointing to the management network, which should not be a publicly routable subnet and, as such, is not reachable to the instances, making Software Deployment impossible.
Changing those parameters to the public URL and restarting heat-api solved the problem.
Example:
# Complete public Identity API endpoint. (string value)
#auth_uri = <None>
#auth_uri = http://<ip of mangement network>:5000/v2.0
auth_uri = https://<cloud.
Changed in fuel: | |
assignee: | nobody → Fuel Library Team (fuel-library) |
milestone: | none → 7.0-updates |
importance: | Undecided → High |
status: | New → Confirmed |
tags: | added: area-library |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → MOS Puppet Team (mos-puppet) |
tags: |
added: area-mos removed: area-library |
Changed in fuel: | |
milestone: | 7.0-updates → 9.0 |
status: | Confirmed → New |
Changed in fuel: | |
assignee: | Registry Administrators (registry) → nobody |
To post a comment you must log in.
From latest 8.0 env (372 ISO):
# Complete public Identity API endpoint. (string value) 172.16. 164.213: 5000/v2. 0/
#auth_uri = <None>
auth_uri = http://
it is set to public endpoint.