heat unable to communicate with ampq rabbit server

Bug #1719571 reported by Mohit
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
New
Undecided
Mohit

Bug Description

Environment -:
--------------
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS"

$ grep ^ /etc/apt/sources.list /etc/apt/sources.list.d/*
---snip
/etc/apt/sources.list.d/cloudarchive-ocata.list:deb http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/ocata main
/etc/apt/sources.list.d/cloudarchive-ocata.list:# deb-src http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/ocata main

$ heat --version
1.8.0

$ pip freeze|grep heat
heat==8.0.2
heat-cfntools==1.2.7
python-heatclient==1.8.0

$ dpkg -l |grep rabbit
ii rabbitmq-server 3.5.7-1ubuntu0.16.04.2 all AMQP server written in Erlang

Steps to reproduce -:
----------------------
1.Install heat packages following octa installation guide for ubuntu
2. execute openstack stack list
3. Getting error message
ERROR: Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'openstack' in vhost '/openstack': received 'false' but current is 'true'

4. On rabbitmq logs
=ERROR REPORT==== 26-Sep-2017::16:20:11 ===
Channel error on connection <0.31698.5> (192.168.179.133:54012 -> 192.168.179.133:5672, vhost: '/openstack', user: 'openstack'), channel 1:
{amqp_error,precondition_failed,
            "inequivalent arg 'durable' for exchange 'openstack' in vhost '/openstack': received 'false' but current is 'true'",
            'exchange.declare'}

Workaround -:
-------------
1. Update heat.conf default section with rabbit_durable_queues = true
2. Restart the heat services

Expectations -:
----------------
The documentation page https://docs.openstack.org/project-install-guide/orchestration/ocata/install-ubuntu.html

should have listed out to set the param rabbit_durable_queues = true

Do see if you can reproduce this issue further.

Changed in heat:
assignee: nobody → Mohit (mohit.mohit2atcognizant.com)
Revision history for this message
Shi Yan (yanshi-403) wrote :

Hi, Mohit

I think this may be related to rabbit implementation.
The "durable" status is actually decided when the exchange/queue is set up.

So if you delete the heat used exchange or queue in rabbitmq server, the mq connection will be established again. That should be working fine.

Rico Lin (rico-lin)
Changed in heat:
milestone: none → no-priority-tag-bugs
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.