Back to bug 1370300
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Libor Miksik | 2016-08-30 17:53:48 UTC | Status | NEW | POST |
| CC | mreynolds | |||
| Assignee | nhosoi | mreynolds | ||
| Doc Text | Cause: The replication update status of a replication agreement when an error occurred only display a generic message | |||
| Doc Text | , then the error could of been by many different conditions. Consequence: Troubleshooting the replication agreement failure is very difficult. Fix: When an error occurs update the agreement status with a detailed message. Result: All replication | |||
| Doc Text | agreement update failures are correctly and precisely logged. | |||
| Doc Type | If docs needed, set a value | Bug Fix | ||
| CC | lmiksik | |||
| Noriko Hosoi | 2016-08-30 19:50:05 UTC | Status | POST | MODIFIED |
| Fixed In Version | 389-ds-base-1.3.5.10-9.el7 | |||
| errata-xmlrpc | 2016-08-30 19:54:21 UTC | Status | MODIFIED | ON_QA |
| Viktor Ashirov | 2016-09-01 08:56:33 UTC | Status | ON_QA | ASSIGNED |
| Noriko Hosoi | 2016-09-01 19:44:17 UTC | Status | ASSIGNED | POST |
| Status | POST | MODIFIED | ||
| Fixed In Version | 389-ds-base-1.3.5.10-9.el7 | 389-ds-base-1.3.5.10-10.el7 | ||
| Noriko Hosoi | 2016-09-01 19:45:16 UTC | Status | MODIFIED | ON_QA |
| Sankar Ramalingam | 2016-09-13 13:41:16 UTC | Status | ON_QA | VERIFIED |
| CC | sramling | |||
| Sankar Ramalingam | 2016-09-13 18:40:45 UTC | Flags | needinfo?(mreynolds) | |
| Petr Bokoc | 2016-09-29 14:49:53 UTC | Flags | needinfo?(mreynolds) | |
| CC | pbokoc | |||
| Docs Contact | pbokoc | |||
| Petr Bokoc | 2016-10-06 10:27:06 UTC | Docs Contact | pbokoc | apetrova |
| Aneta Šteflová Petrová | 2016-10-12 13:44:55 UTC | Doc Text | Cause: The replication update status of a replication agreement when an error occurred only display a generic message, then the error could of been by many different conditions. Consequence: Troubleshooting the replication agreement failure is very difficult. Fix: When an error occurs update the agreement status with a detailed message. Result: All replication agreement update failures are correctly and precisely logged. | Replication agreement update status now includes details about replication agreement failures The replication agreement update status previously only displayed a generic message after an error occurred, which made troubleshooting the replication agreement failure difficult. Now, the update status includes a detailed error message. As a result, all replication agreement update failures are correctly and precisely logged. |
| Flags | needinfo?(mreynolds) | |||
| Aneta Šteflová Petrová | 2016-10-12 15:41:17 UTC | Flags | needinfo?(mreynolds) | |
| Doc Text | Replication agreement update status now includes details about replication agreement failures The replication agreement update status previously only displayed a generic message after an error occurred, which made troubleshooting the replication agreement failure difficult. Now, the update status includes a detailed error message. As a result, all replication agreement update failures are correctly and precisely logged. | Replication agreement update status now includes details about replication agreement failures The replication agreement update status previously displayed only a generic message after an error occurred, which made troubleshooting the replication agreement failure difficult. Now, the update status includes a detailed error message. As a result, all replication agreement update failures are correctly and precisely logged. |
||
| errata-xmlrpc | 2016-11-02 12:29:34 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-11-03 20:45:20 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-11-03 16:45:20 UTC | |||
| Marc Sauton | 2016-12-06 22:57:13 UTC | CC | msauton | |
| Simon Pichugin | 2020-09-13 21:49:31 UTC | Link ID | Github 389ds/389-ds-base/issues/2016 |
Back to bug 1370300