Fuel for OpenStack

astute will stop receive new messages if queue is redeclared

Bug #1340555 reported by Dima Shulyak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Committed
High
Dima Shulyak
Fuel for OpenStack 5.1
5.0.x
Won't Fix
Medium
Dima Shulyak
Fuel for OpenStack 5.0.2

Bug Description

After queues is being redeclared astute cant accept new messages.
But we need to redeclare queue/exchanges on precondition failure, as solution for https://bugs.launchpad.net/fuel/+bug/1319451.

To resolve this issue we need:

1. implement ccn [1] in astute
2. package 1.4.1 version of ruby-amqp, as mentioned in this mailing list ruby-amqp driver supports ccn only starting from 0.9.5

[1] http://www.rabbitmq.com/consumer-cancel.html
[2] https://groups.google.com/forum/#!topic/ruby-amqp/81phyuMJTv8

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-astute (master)

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

Changed in fuel:
status: New → In Progress
Revision history for this message
Mike Scherbakov (mihgen) wrote :

Does it affect 5.0.1?

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-web (master)

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

Dmitry Pyzhov (dpyzhov)
tags: added: release-notes
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to fuel-main (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/106936

Dmitry Pyzhov (dpyzhov)
no longer affects: fuel/5.1.x
Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

https://bugs.launchpad.net/bugs/1341510 OSCI bug for amqp library

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to fuel-main (master)

Reviewed: https://review.openstack.org/106936
Committed: https://git.openstack.org/cgit/stackforge/fuel-main/commit/?id=df55a67cec68b1bd8a7400ee73f2c3652a219e9b
Submitter: Jenkins
Branch: master

commit df55a67cec68b1bd8a7400ee73f2c3652a219e9b
Author: Dima Shulyak <email address hidden>
Date: Tue Jul 15 08:48:52 2014 +0300

    Change ruby-amqp version to 1.4.1 in astute spec

    Change-Id: I8305870b3552199745c256694a1785d71d3fcf00
    Related-Bug: #1340555
    Related-Bug: #1341510

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-astute (master)

Reviewed: https://review.openstack.org/106291
Committed: https://git.openstack.org/cgit/stackforge/fuel-astute/commit/?id=6498789c89c9bdbf7300da157ed457e8c0e1919c
Submitter: Jenkins
Branch: master

commit 6498789c89c9bdbf7300da157ed457e8c0e1919c
Author: Dima Shulyak <email address hidden>
Date: Fri Jul 11 10:22:15 2014 +0300

    Implement consumer cancel notification in astute

    - auto_recover exchange/queue in case of consumer canceled queue
    - amqp dependency changed to 1.4.1
    - autorecovery performed for each each exchange/queue

    Change-Id: I28d44841a207585d5d7b4a7920b58132be7b7394
    Closes-Bug: #1340555

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-web (master)

Reviewed: https://review.openstack.org/106350
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=84112e4f4a80c4433b0c4adf271fe60fa7f02819
Submitter: Jenkins
Branch: master

commit 84112e4f4a80c4433b0c4adf271fe60fa7f02819
Author: Dima Shulyak <email address hidden>
Date: Fri Jul 11 14:59:56 2014 +0300

    Drop both exchanges used by naily

    - deleting both exchanges in case of precondition failure

    Naily will be able to auto_recover using consumer cancel notifications

    For additional info look at astute patch and correcponding bug:
      I28d44841a207585d5d7b4a7920b58132be7b7394

    Change-Id: I77c24badaa09ab73d83316ec4665df393966322e
    Partial-Bug: #1340555

Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

Affects only 5.0.2 master node and does not affects 5.1 master node with 5.0.2 environments, setting Medium priority for 5.0.x series.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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