[SRU] update to 1.8.3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo.messaging (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Vivid |
Fix Released
|
Medium
|
Unassigned |
Bug Description
OpenStack have released two point releases to oslo.messaging, resolving a number of rabbitmq and zeromq driver bugs:
1.8.3
-----
* Adding Publisher Acknowledgement
* consumer connections not closed properly
* rabbit: Set timeout on the underlying socket
* Updated from global requirements
1.8.2
-----
* rabbit: add some notes about heartbeat
* Disable and mark heartbeat as experimental
* rabbit: fix ipv6 support
* Fix changing keys during iteration in matchmaker heartbeat << already holding cherry pick
* Add pluggability for matchmakers << already holding cherry pick
* Don't raise Timeout on no-matchmaker results
* Fix the bug redis do not delete the expired keys
* set defaultbranch for reviews
This seems appropriate for SRU without cherry picking back to 1.8.1.
Related branches
description: | updated |
Changed in oslo.messaging (Ubuntu): | |
importance: | Undecided → High |
Changed in oslo.messaging (Ubuntu): | |
status: | New → Fix Released |
Changed in oslo.messaging (Ubuntu Vivid): | |
importance: | Undecided → Medium |
tags: |
added: verification-done removed: verification-needed |
Hello James, 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/ PerformingSRUVe rification . Thank you in advance!