Activity log for bug #1296922
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2014-03-24 20:00:08 | Dmitry Borodaenko | bug | added bug | ||
| 2014-03-24 20:01:55 | Dmitry Borodaenko | fuel: milestone | 5.0 | ||
| 2014-03-24 20:02:02 | Dmitry Borodaenko | tags | ha | backports-4.1.1 ha | |
| 2014-03-24 20:19:55 | Dmitry Borodaenko | fuel: importance | Critical | Medium | |
| 2014-03-24 20:20:24 | Dmitry Borodaenko | tags | backports-4.1.1 ha | ha | |
| 2014-03-24 20:28:41 | Dmitry Borodaenko | summary | RabbitMQ queues are not synchronized after failback | RabbitMQ 3.x queues are not synchronized | |
| 2014-03-24 20:30:32 | Dmitry Borodaenko | description | Even though OpenStack creates all queues synchronized across all controller nodes, after RabbitMQ is restarted on a node, queues are no longer synchronized to that node. See comments #40-#45 in https://bugs.launchpad.net/fuel/+bug/1285449 for more details. | Even though OpenStack creates all queues synchronized across all controller nodes, after RabbitMQ is restarted on a node, queues are no longer synchronized to that node. See comments #40-#45 in https://bugs.launchpad.net/fuel/+bug/1285449 for more details. Update: the problem is only present with RabbitMQ 3.x. | |
| 2014-03-24 20:33:45 | Dmitry Borodaenko | fuel: status | Confirmed | Triaged | |
| 2014-04-15 18:22:47 | Dmitry Borodaenko | tags | ha | backports-4.1.1 ha | |
| 2014-04-15 18:22:52 | Dmitry Borodaenko | fuel: status | Triaged | In Progress | |
| 2014-04-15 18:22:56 | Dmitry Borodaenko | fuel: milestone | 5.0 | 4.1.1 | |
| 2014-04-24 01:33:37 | Dmitry Borodaenko | fuel: status | In Progress | Fix Committed | |
| 2014-04-30 23:55:45 | Amanda Gomes | bug | added subscriber Amanda Gomes | ||
| 2014-05-08 12:14:15 | Mike Scherbakov | tags | backports-4.1.1 ha | backports-4.1.1 ha release-notese |
