Back to bug 1003759
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Krutika Dhananjay | 2013-09-03 09:26:27 UTC | Status | NEW | ASSIGNED |
| CC | kdhananj | |||
| Assignee | amarts | kdhananj | ||
| Krutika Dhananjay | 2013-09-03 09:54:32 UTC | Status | ASSIGNED | POST |
| Amar Tumballi | 2013-09-05 07:19:05 UTC | Priority | unspecified | high |
| CC | amarts | |||
| Amar Tumballi | 2013-09-06 06:23:25 UTC | Status | POST | MODIFIED |
| Krutika Dhananjay | 2013-09-19 11:27:36 UTC | Status | MODIFIED | ON_QA |
| Fixed In Version | glusterfs-v3.4.0.31rhs | |||
| Vivek Agarwal | 2013-10-03 08:57:18 UTC | Keywords | ZStream | |
| Fixed In Version | glusterfs-v3.4.0.31rhs | glusterfs-3.4.0.33rhs-1 | ||
| Gowrishankar Rajaiyan | 2013-10-03 09:57:37 UTC | CC | grajaiya | |
| QA Contact | sdharane | saujain | ||
| SATHEESARAN | 2013-10-07 11:37:56 UTC | Status | ON_QA | VERIFIED |
| CC | sasundar | |||
| QA Contact | saujain | sasundar | ||
| Krutika Dhananjay | 2013-10-09 09:25:39 UTC | Doc Text | Cause: This happened because of incorrect aggregation of responses received from peers by the originator glusterd. Consequence: Setting limits on a single brick volume in an n node cluster (n > 1) OR on a volume in an n node cluster (n>1) where all bricks reside on the same node fails with the error Fix: The aggregation of peers' responses is done correctly now. Result: Setting limits in configurations of the kind described in 'Consequence' field will work with this fix. |
|
| Anjana Suparna Sriram | 2013-11-11 11:26:31 UTC | CC | asriram | |
| Doc Text | Cause: This happened because of incorrect aggregation of responses received from peers by the originator glusterd. Consequence: Setting limits on a single brick volume in an n node cluster (n > 1) OR on a volume in an n node cluster (n>1) where all bricks reside on the same node fails with the error Fix: The aggregation of peers' responses is done correctly now. Result: Setting limits in configurations of the kind described in 'Consequence' field will work with this fix. | Previously, setting limits on a single brick volume or on a volume where all bricks reside on the same node, in a cluster with more than one node, failed due to the incorrect aggregation logic for quota sub command. Now, with this update setting limits is successful. | ||
| errata-xmlrpc | 2013-11-27 15:36:37 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2013-11-27 10:36:37 UTC | |||
| John Skeoch | 2016-01-19 06:12:43 UTC | CC | mzywusko |
Back to bug 1003759