Back to bug 1000903
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Saurabh | 2013-08-26 05:26:50 UTC | CC | rhs-bugs, vbellur | |
| Component | redhat-access-plugin-storage | glusterfs-server | ||
| Assignee | kroberts | amarts | ||
| krishnan parthasarathi | 2013-09-02 06:28:42 UTC | CC | kparthas | |
| Assignee | amarts | kdhananj | ||
| Vivek Agarwal | 2013-09-19 09:49:02 UTC | Assignee | kdhananj | rhs-bugs |
| Vivek Agarwal | 2013-09-24 09:59:50 UTC | CC | vagarwal | |
| Scott Haines | 2013-09-24 12:42:25 UTC | Keywords | ZStream | |
| Raghavendra G | 2013-10-04 10:43:00 UTC | CC | rgowdapp | |
| Assignee | rhs-bugs | vshastry | ||
| Sudhir D | 2013-10-08 06:23:55 UTC | QA Contact | sdharane | saujain |
| Anuradha | 2013-10-16 04:48:32 UTC | CC | atalur | |
| Assignee | vshastry | atalur | ||
| Anuradha | 2013-10-17 07:21:23 UTC | Status | NEW | ASSIGNED |
| Anuradha | 2013-10-21 11:31:48 UTC | Status | ASSIGNED | POST |
| Anuradha | 2013-10-21 12:29:40 UTC | Doc Text | Cause: Volume reset command resets only unprotected fields when "force" option is not specified. Consequence: As quota is a "protected" field and "force" option is required in order to reset protected fields, when "force" option was not given (with quota enabled)for volume reset command, the command failed. Fix: A separate case to handle reset of the "protected" fields was added. Result: Volume reset command doesn't fail without "force" option even when the protected fields are set. A message is displayed indicating that "force" should be used to reset the protected fields. |
|
| Vivek Agarwal | 2013-10-22 15:56:42 UTC | Status | POST | ON_QA |
| Anuradha | 2013-10-23 05:45:51 UTC | Status | ON_QA | POST |
| Anuradha | 2013-10-24 09:08:46 UTC | Blocks | 1022905 | |
| Anuradha | 2013-10-29 09:24:38 UTC | Status | POST | MODIFIED |
| Amar Tumballi | 2013-10-30 18:40:50 UTC | Status | MODIFIED | ON_QA |
| Fixed In Version | glusterfs-3.4.0.37rhs-1 | |||
| Saurabh | 2013-10-31 12:50:52 UTC | Status | ON_QA | VERIFIED |
| Vivek Agarwal | 2013-11-08 08:51:16 UTC | Priority | unspecified | high |
| krishnan parthasarathi | 2013-11-22 12:27:42 UTC | Doc Text | Cause: Volume reset command resets only unprotected fields when "force" option is not specified. Consequence: As quota is a "protected" field and "force" option is required in order to reset protected fields, when "force" option was not given (with quota enabled)for volume reset command, the command failed. Fix: A separate case to handle reset of the "protected" fields was added. Result: Volume reset command doesn't fail without "force" option even when the protected fields are set. A message is displayed indicating that "force" should be used to reset the protected fields. | Previously, volume reset command failed when there were protected options set on the volume. Quota is a protected field and the reset command would fail when quota is enabled on the volume. Now, with this update, volume reset command doesn't fail without "force" option even when the protected fields are set. A message is displayed indicating that "force" should be used to reset the protected fields. |
| errata-xmlrpc | 2013-11-27 15:32:34 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2013-11-27 10:32:34 UTC | |||
| John Skeoch | 2016-01-19 06:12:43 UTC | CC | mzywusko | |
| John Skeoch | 2016-09-20 02:00:07 UTC | CC | smohan |
Back to bug 1000903