Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1049504

Summary:	Heat API qpid errors after reboot
Product:	Red Hat OpenStack	Reporter:	Steven Dake <sdake>
Component:	openstack-heat	Assignee:	Steven Hardy <shardy>
Status:	CLOSED NOTABUG	QA Contact:	Kevin Whitney <kwhitney>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.0	CC:	jpeeler, sbaker, sdake, shardy, srevivo, yeylon
Target Milestone:	z1	Keywords:	ZStream
Target Release:	4.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1049488	Environment:
Last Closed:	2014-01-13 16:47:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1049488, 1055660
Bug Blocks:

Description Steven Dake 2014-01-07 16:16:44 UTC

+++ This bug was initially created as a clone of Bug #1049488 +++

Description of problem:
After reboot, heat is broken because it can't connect to the qpid broker - I'm not sure if this is a heat or qpid issue, but it doesn't seem to affect all the other services, e.g glance and keystone still work (although nova seems to have similar issues)

Version-Release number of selected component (if applicable):
# rpm -qa | grep -e heat -e packstack
openstack-heat-common-2013.2-1.0.fc20.noarch
openstack-heat-api-cfn-2013.2-1.0.fc20.noarch
openstack-heat-api-cloudwatch-2013.2-1.0.fc20.noarch
python-heatclient-0.2.6-2.fc20.noarch
openstack-heat-engine-2013.2-1.0.fc20.noarch
openstack-packstack-2013.2.1-0.25.dev936.fc20.noarch
openstack-heat-api-2013.2-1.0.fc20.noarch


How reproducible:
Always, seems broken after every reboot.


Steps to Reproduce:
1. Install F20 (bare metal box w/16G ram, selected development tools)
2. sudo su -
3. yum -y update
4. shutdown -r now (reboot to ensure all updates are active)
4. yum -y install openstack-packstack
5. packstack --allinone --os-heat-install=y --os-swift-install=n --os-ceilometer-install=y --os-heat-cloudwatch-install=y --os-heat-cfn-install=y
6. reboot

Actual results:
# tail -f /var/log/heat/api.log 
2014-01-07 15:45:08.599 1635 INFO urllib3.connectionpool [-] Starting new HTTP connection (1): 192.168.0.11
2014-01-07 15:45:08.643 1635 ERROR heat.openstack.common.rpc.impl_qpid [-] Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Sleeping 1 seconds
2014-01-07 15:45:09.645 1635 ERROR heat.openstack.common.rpc.impl_qpid [-] Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Sleeping 2 seconds
2014-01-07 15:45:11.648 1635 ERROR heat.openstack.common.rpc.impl_qpid [-] Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Sleeping 4 seconds

Expected results:
Heat should be fully operational after reboot.

Additional info:

This workaround gets heat working again:
# service qpidd restart
# service openstack-heat-engine restart
# service openstack-heat-api restart

Comment 2 Steven Dake 2014-01-09 23:19:27 UTC

Steve,

I believe last we spoke this was a bug in Fedora 20 only, not in RHEL.  If that is the case, feel free to close this as not a bug.

Regards
-steve

Comment 3 Steven Hardy 2014-01-13 16:47:20 UTC

(In reply to Steven Dake from comment #2)
> Steve,
> 
> I believe last we spoke this was a bug in Fedora 20 only, not in RHEL.  If
> that is the case, feel free to close this as not a bug.
> 
> Regards
> -steve

I've tested with RHOS on RHEL 6.5, and I cannot reproduce the issue, so closing this not a bug - it would appear that it is a Fedora specific problem.