AMQPChannelException: (406, u"PRECONDITION_FAILED - parameters for queue 'notifications.info' in vhost '/' not equivalent", (50, 10), 'Channel.queue_declare')

Bug #1086167 reported by Nachi Ueno
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
devstack
Fix Released
Undecided
Nachi Ueno

Bug Description

When I trying to test floating ip. I got followings on quantum-server

2012-12-03 13:59:13 907 TRACE quantum.openstack.common.notifier.rpc_notifier AMQPChannelException: (406, u"PRECONDITION_FAILED - parameters for queue 'notifications.info' in vhost '/' not equivalent", (50, 10), 'Channel.queue_declare')
2012-12-03 13:59:13 907 TRACE quantum.openstack.common.notifier.rpc_notifier
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/poll.py", line 97, in wait
    readers.get(fileno, noop).cb(fileno)
  File "/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 192, in main
    result = function(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/amqplib/client_0_8/channel.py", line 1294, in queue_declare
    (50, 11), # Channel.queue_declare_ok
  File "/usr/local/lib/python2.7/dist-packages/amqplib/client_0_8/abstract_channel.py", line 105, in wait
    return amqp_method(self, args)
  File "/usr/local/lib/python2.7/dist-packages/amqplib/client_0_8/channel.py", line 273, in _close
    (class_id, method_id))
AMQPChannelException: (406, u"PRECONDITION_FAILED - parameters for queue 'notifications.info' in vhost '/' not equivalent", (50, 10), 'Channel.queue_declare')

- How to reproduce
Use this localrc

DEST=/opt/stack
disable_service n-net
disable_service horizon
enable_service q-svc
enable_service q-agt
enable_service q-dhcp
enable_service q-l3
enable_service quantum
#disable_service rabbitmq
#enable_service qpid
API_RATE_LIMIT=False
VOLUME_BACKING_FILE_SIZE=4G
FIXED_RANGE=10.1.0.0/24
FIXED_NETWORK_SIZE=256
VIRT_DRIVER=libvirt
SWIFT_REPLICAS=1
export OS_NO_CACHE=True
SCREEN_LOGDIR=/opt/stack/screen-logs
SYSLOG=True
SKIP_EXERCISES=boot_from_volume,client-env
ROOTSLEEP=0
ACTIVE_TIMEOUT=60
BOOT_TIMEOUT=90
ASSOCIATE_TIMEOUT=60
ADMIN_PASSWORD=openstack
MYSQL_PASSWORD=openstack
RABBIT_PASSWORD=openstack
SERVICE_PASSWORD=openstack
SERVICE_TOKEN=tokentoken
Q_PLUGIN=openvswitch
#Q_PLUGIN=linuxbridge
Q_USE_DEBUG_COMMAND=True
NETWORK_GATEWAY=10.1.0.1

Run
./exercises/floating_ips.sh

Revision history for this message
Nachi Ueno (nati-ueno) wrote :

It seems glance bug is related.
https://bugs.launchpad.net/glance/+bug/1057325

However the fix is already in quantum...

Revision history for this message
Nachi Ueno (nati-ueno) wrote :

You can reproduce just using
quantum floatingip-create.

dan wendlandt (danwent)
Changed in quantum:
importance: Undecided → Critical
Revision history for this message
Nachi Ueno (nati-ueno) wrote :

Actually, this was configuration problem.

Following fixes the problem

Uninstall rabbitmq
delete /var/lib/rabbitmq

reinstall rabbitmq

/etc/quantum/quantum.conf
rabbit_durable_queues = True

Changed in quantum:
assignee: nobody → Nachi Ueno (nati-ueno)
Changed in devstack:
assignee: nobody → Nachi Ueno (nati-ueno)
Changed in devstack:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to devstack (master)

Fix proposed to branch: master
Review: https://review.openstack.org/17424

Revision history for this message
yong sheng gong (gongysh) wrote :

I am wondering why we need to do it, we have run quantum without it for a long time. We need to investigate more about this bug to make sure why we have this bug now.

Revision history for this message
Gary Kotton (garyk) wrote :

Glance made a change about two weeks ago. This was the cause of all of the problems.

Revision history for this message
Gary Kotton (garyk) wrote :

This has been dealt with by https://review.openstack.org/#/c/17469/
Thanks
Gary

Changed in quantum:
status: New → Invalid
Changed in devstack:
status: In Progress → Fix Committed
no longer affects: quantum
Dean Troyer (dtroyer)
Changed in devstack:
status: Fix Committed → Fix Released
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.