heat-api fails to start if Keystone is unavailable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Johannes Grassler |
Bug Description
Problem Description
===================
If Keystone is unavailable when heat-api starts up, heat-api aborts with the following error (see attachment for a full traceback):
2016-02-26 10:59:23.817 25251 CRITICAL heat-api [-] ConnectionRefused: Unable to establish connection to http://
The problem was introduced by this commit:
https:/
The auth_url catalog lookup introduced by this commit may fail, and there is no
retrying, which causes heat-api to exit if Keystone is unreachable, even
temporarily.
Steps to reproduce
==================
Note: this assumes a non-HA cloud with one controller where both heat-api and
Keystone run on the same machine. On this machine run the following command:
# systemctl restart openstack-keystone openstack-
Now look in /var/log/
happens because it takes a few seconds for the TCP listeners to be up after
/usr/bin/
Environment
===========
Openstack Liberty on SLES 12.1
Package versions:
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
Changed in heat: | |
milestone: | none → mitaka-rc1 |
importance: | Undecided → Medium |
Fix proposed to branch: master /review. openstack. org/287302
Review: https:/