Consumers for re-balanced pipeline queues are not cleaned

currently debugging but it seems like when .wait() is called on consumer (after stop) it fails.

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

ceilometer calls stop() then wait() when killing consumers...

when using 1.8.2: oslo.messaging is throwing "ERROR oslo_messaging._drivers.impl_rabbit [-] Failed to consume message from queue:" (with no error message) when caling wait()

against master: nothing is thrown... but consumers are not killed.

Fix proposed to branch: stable/kilo
Review: https://review.openstack.org/185702

Reviewed: https://review.openstack.org/185693
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=a45084126452c7ce2a7da43e09a2654f2ee9ec2d
Submitter: Jenkins
Branch: master

commit a45084126452c7ce2a7da43e09a2654f2ee9ec2d
Author: gordon chung <email address hidden>
Date: Tue May 26 14:36:23 2015 -0400

    consumer connections not closed properly

    heartbeat_thread is not set for listeners. when closing connection,
    it blindly checks heartbeat_thread and will throw an error causing
    connection to remain open. this patch explicitly sets
    heartbeat_thread to None.

    Change-Id: Ief3bf02f952882ecadf742cdd0bac8edd7812473
    Closes-Bug: #1458917

Reviewed: https://review.openstack.org/185702
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=41d0d875a10b48eea89f46ae3c426a023dfae27c
Submitter: Jenkins
Branch: stable/kilo

commit 41d0d875a10b48eea89f46ae3c426a023dfae27c
Author: gordon chung <email address hidden>
Date: Tue May 26 14:36:23 2015 -0400

    consumer connections not closed properly

    heartbeat_thread is not set for listeners. when closing connection,
    it blindly checks heartbeat_thread and will throw an error causing
    connection to remain open. this patch explicitly sets
    heartbeat_thread to None.

    Change-Id: Ief3bf02f952882ecadf742cdd0bac8edd7812473
    Closes-Bug: #1458917

Hello Yurii, or anyone else affected,

Accepted oslo.messaging into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/oslo.messaging/1.8.3-0ubuntu0.15.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

This bug was fixed in the package oslo.messaging - 1.8.3-0ubuntu0.15.04.1

---------------
oslo.messaging (1.8.3-0ubuntu0.15.04.1) vivid; urgency=medium

  * New upstream point release (LP: #1467959):
    - RabbitMQ driver:
      + Adding publisher acknowledgements/confirms for better handling
        of messages during broker shutdown/network failure.
      + Ensure consumer connections closed properly (LP: #1458917).
      + Set timeout on the underlying socket (LP: #1436788).
      + Disable and mark heartbeat as experimental (LP: #1436769).
      + Fix ipv6 support.
    - ZeroMQ driver:
      + Don't raise Timeout on no-matchmaker results (LP: #1186310).
      + Fix issue with Redis not deleting expired keys (LP: #1417464).
      + d/p/Fix-changing-keys-during-iteration-in-matchmaker-hea.patch,
        d/p/Add-pluggability-for-matchmakers.patch: Dropped, included
        upstream.

 -- James Page <email address hidden> Tue, 23 Jun 2015 15:28:01 +0100

The verification of the Stable Release Update for oslo.messaging has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Hello Yurii, or anyone else affected,

Accepted oslo.messaging into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/oslo.messaging/1.8.3-0ubuntu0.15.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

This issue was fixed in the openstack/oslo.messaging 1.8.3 release.