Back to bug 1310248
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| John Prause | 2016-02-19 20:58:07 UTC | Status | NEW | ASSIGNED |
| Target Release | 5.6.0 | 5.5.4 | ||
| Assignee | gblomqui | lsmola | ||
| John Prause | 2016-02-19 20:58:36 UTC | Target Release | 5.5.4 | 5.4.5 |
| Greg Blomquist | 2016-03-04 15:30:06 UTC | Status | ASSIGNED | POST |
| John Prause | 2016-03-04 15:49:43 UTC | Status | POST | MODIFIED |
| errata-xmlrpc | 2016-03-07 21:29:28 UTC | Status | MODIFIED | ON_QA |
| John Prause | 2016-03-17 17:07:34 UTC | Fixed In Version | 5.4.5.2 | |
| dajohnso | 2016-03-18 09:44:13 UTC | QA Contact | dajohnso | jteehan |
| Pete Savage | 2016-03-18 09:45:41 UTC | QA Contact | jteehan | mcornea |
| Marius Cornea | 2016-03-18 09:46:43 UTC | QA Contact | mcornea | rrasouli |
| Marianne Feifer | 2016-03-21 15:10:39 UTC | CC | mfeifer | |
| Doc Text | Cause: Bunny gemcouldn't handle reconnect when amqp service got restarted. Consequence: AMQP connection doesn't recover after rabbitmq-server restart Fix: Update bunny gem. Result: AMQP connection recovers. |
|||
| Suyog Sainkar | 2016-03-22 02:21:44 UTC | CC | ssainkar | |
| Doc Text | Cause: Bunny gemcouldn't handle reconnect when amqp service got restarted. Consequence: AMQP connection doesn't recover after rabbitmq-server restart Fix: Update bunny gem. Result: AMQP connection recovers. | Previously, the AMQP connection did not recover after rabbitmq-server restart. This was because the previous Bunny gem couldn't handle a reconnect when AMQP service got restarted. This patch updated the Bunny gem and the AMQP connection now recovers as expected. | ||
| Ronnie Rasouli | 2016-03-29 07:56:13 UTC | Status | ON_QA | VERIFIED |
| errata-xmlrpc | 2016-03-29 13:57:32 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-03-29 14:18:28 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-03-29 10:18:28 UTC | |||
| Dave Johnson | 2017-08-30 03:45:26 UTC | QA Contact | rrasouli | opavlenk |
Back to bug 1310248