Back to bug 1294751
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla Rules Engine | 2015-12-30 06:05:00 UTC | Keywords | ZStream | |
| Vijaikumar Mallikarjuna | 2015-12-30 06:05:30 UTC | Status | NEW | ASSIGNED |
| CC | vmallika | |||
| Assignee | vagarwal | vmallika | ||
| Vivek Agarwal | 2015-12-30 07:11:01 UTC | CC | vagarwal | |
| Vivek Agarwal | 2016-01-07 07:19:56 UTC | Assignee | vmallika | vagarwal |
| Vijaikumar Mallikarjuna | 2016-01-17 12:57:47 UTC | Blocks | 1299184 | |
| Manikandan | 2016-01-28 07:17:30 UTC | CC | mselvaga | |
| Assignee | vagarwal | mselvaga | ||
| Manikandan | 2016-01-28 07:18:20 UTC | Blocks | 1302554 | |
| Vijaikumar Mallikarjuna | 2016-02-02 11:01:45 UTC | Status | ASSIGNED | POST |
| Manikandan | 2016-02-10 06:43:51 UTC | Blocks | 1306136 | |
| John Skeoch | 2016-02-18 00:11:21 UTC | CC | vagarwal | sankarshan |
| Rahul Hinduja | 2016-03-04 12:22:03 UTC | CC | rhinduja | |
| Rejy M Cyriac | 2016-03-08 07:57:35 UTC | CC | rcyriac | |
| Red Hat Bugzilla Rules Engine | 2016-03-08 08:15:51 UTC | Target Release | --- | RHGS 3.1.3 |
| Rahul Hinduja | 2016-03-27 14:37:42 UTC | QA Contact | storage-qa-internal | ashah |
| Sat6QE Jenkins | 2016-03-28 20:15:54 UTC | Status | POST | MODIFIED |
| Mike McCune | 2016-03-28 23:10:48 UTC | Status | MODIFIED | POST |
| Vijaikumar Mallikarjuna | 2016-04-07 03:03:22 UTC | Status | POST | MODIFIED |
| errata-xmlrpc | 2016-04-20 11:23:26 UTC | Status | MODIFIED | ON_QA |
| Satish Mohan | 2016-04-20 11:29:08 UTC | Fixed In Version | glusterfs-3.7.9-2 | |
| Anil Shah | 2016-04-26 06:23:29 UTC | Status | ON_QA | VERIFIED |
| Anil Shah | 2016-04-26 06:32:10 UTC | Status | VERIFIED | ON_QA |
| Anil Shah | 2016-04-26 07:18:24 UTC | Status | ON_QA | VERIFIED |
| John Skeoch | 2016-05-11 22:50:15 UTC | CC | vmallika | smohan |
| Manikandan | 2016-05-13 10:36:53 UTC | Doc Text | Previously, when quota limit value is set to 0, quota assumes that limit is not set and enforcing was not done. The patch fixes this issue by restricting the user from setting limit values less than or equal to zero. | |
| Laura Bailey | 2016-06-09 04:00:16 UTC | Doc Text | Previously, when quota limit value is set to 0, quota assumes that limit is not set and enforcing was not done. The patch fixes this issue by restricting the user from setting limit values less than or equal to zero. | When the quota limit is set to zero, quota enforcement is disabled, rather than enforcing a quota limit of 0 and preventing any writes. To prevent confusion when using this option, numbers smaller than or equal to zero are no longer valid values. |
| Flags | needinfo?(mselvaga) | |||
| Manikandan | 2016-06-09 05:47:18 UTC | Flags | needinfo?(mselvaga) | |
| errata-xmlrpc | 2016-06-23 00:46:37 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-06-23 05:00:54 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-06-23 01:00:54 UTC | |||
| Rejy M Cyriac | 2016-09-17 12:42:21 UTC | CC | rhs-bugs, storage-qa-internal | |
| Component | gluster-quota | quota | ||
| John Skeoch | 2016-11-23 23:12:16 UTC | CC | mzywusko |
Back to bug 1294751