Bug 1265417 - When rabbitmq is partitionned, heat-apis will break and never come back
Summary: When rabbitmq is partitionned, heat-apis will break and never come back
Keywords:
Status: CLOSED DUPLICATE of bug 1265418
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-heat
Version: 6.0 (Juno)
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 8.0 (Liberty)
Assignee: Zane Bitter
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-22 21:19 UTC by David Hill
Modified: 2016-04-26 20:33 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-23 13:09:43 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description David Hill 2015-09-22 21:19:20 UTC
Description of problem:
When rabbitmq is partitionned, heat-apis will break and never come back even when the rabbitmq cluster is back to a normal state

Version-Release number of selected component (if applicable):


How reproducible:
Everytime

Steps to Reproduce:
1. Get HA rabbitmq cluster
2. Get heat-api running
3. Partition rabbitmq (iptables, kill a node, etc)
4. Heat breaks, every services breaks
5. Fix rabbit MQ
6. All services comes back but not heat-api

Actual results:
Broken heat-apis

Expected results:
Working heat-apis

Additional info:
We're able to reproduce this issue on request.

Comment 2 Zane Bitter 2015-09-23 13:09:43 UTC

*** This bug has been marked as a duplicate of bug 1265418 ***


Note You need to log in before you can comment on or make changes to this bug.