Back to bug 1005465
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| krishnan parthasarathi | 2013-09-10 06:33:11 UTC | CC | kparthas | |
| Assignee | amarts | kdhananj | ||
| Krutika Dhananjay | 2013-09-12 06:58:04 UTC | Status | NEW | POST |
| Amar Tumballi | 2013-09-16 11:39:55 UTC | Priority | unspecified | high |
| CC | amarts | |||
| Scott Haines | 2013-09-23 20:15:48 UTC | Keywords | ZStream | |
| CC | shaines | |||
| Sudhir D | 2013-09-24 05:45:06 UTC | QA Contact | sdharane | saujain |
| Kaushal | 2013-10-07 11:20:59 UTC | CC | kaushal | |
| krishnan parthasarathi | 2013-10-07 12:27:47 UTC | Status | POST | MODIFIED |
| Vivek Agarwal | 2013-10-08 04:55:38 UTC | Status | MODIFIED | ON_QA |
| Kaushal | 2013-10-08 06:26:30 UTC | Fixed In Version | glusterfs-3.4.0.34rhs-1 | |
| Vivek Agarwal | 2013-10-08 08:43:15 UTC | Fixed In Version | glusterfs-3.4.0.34rhs-1 | glusterfs-3.4.0.34rhs |
| Saurabh | 2013-10-08 12:14:05 UTC | Status | ON_QA | VERIFIED |
| Krutika Dhananjay | 2013-10-09 09:07:17 UTC | Doc Text | Cause: Quota options' ranges were not validated by glusterd before. Consequence: glusterd allowed values outside the allowed range for a given quota option to be set. But the bricks would report errors about invalid values in their logs. Worse still, restarting bricks would fail because of validation failure of the options' value. Fix: glusterd now validates the values of 'default-soft-limit', 'hard-timeout', 'soft-timeout' and 'alert-time' during satge op phase and fail the command if the values supplied to these options were found to be out of valid range. Result: a. Option values falling out of the valid ranges will be rejected. b. CLI reports such error conditions to stderr while also outputting the allowed range. |
|
| Anjana Suparna Sriram | 2013-11-11 11:06:58 UTC | CC | asriram | |
| Doc Text | Cause: Quota options' ranges were not validated by glusterd before. Consequence: glusterd allowed values outside the allowed range for a given quota option to be set. But the bricks would report errors about invalid values in their logs. Worse still, restarting bricks would fail because of validation failure of the options' value. Fix: glusterd now validates the values of 'default-soft-limit', 'hard-timeout', 'soft-timeout' and 'alert-time' during satge op phase and fail the command if the values supplied to these options were found to be out of valid range. Result: a. Option values falling out of the valid ranges will be rejected. b. CLI reports such error conditions to stderr while also outputting the allowed range. | Previously, quota options such as 'default-soft-limit', 'hard-timeout', 'soft-timeout' and 'alert-time' were not validated by glusterd. This resulted in invalid values in the brick volfile and restarting bricks failed due to validation failure of the option's value. Now with this update, glusterd validates the values and rejects any values falling out of range. It also reports the allowed range of values to the CLI. | ||
| errata-xmlrpc | 2013-11-27 15:36:59 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2013-11-27 10:36:59 UTC | |||
| John Skeoch | 2016-01-19 06:12:43 UTC | CC | mzywusko |
Back to bug 1005465