Back to bug 1315583

Who When What Removed Added
Red Hat Bugzilla Rules Engine 2016-03-08 07:05:08 UTC Keywords ZStream
hari gowtham 2016-04-19 07:44:56 UTC Blocks 1328342
hari gowtham 2016-05-24 09:44:43 UTC Status NEW POST
CC hgowtham
Atin Mukherjee 2016-08-03 06:01:59 UTC Sub Component tiering
CC rhs-bugs
Component glusterfs tier
Nithya Balachandran 2017-02-23 06:33:34 UTC CC nbalacha
Blocks 1417147
Atin Mukherjee 2017-02-23 15:03:14 UTC CC amukherj
Alok 2017-02-28 06:26:26 UTC CC asrivast
Rahul Hinduja 2017-03-06 06:56:58 UTC CC rhinduja
Red Hat Bugzilla Rules Engine 2017-03-06 13:12:37 UTC Target Release --- RHGS 3.3.0
Atin Mukherjee 2017-03-30 13:24:39 UTC Assignee rhs-bugs hgowtham
Atin Mukherjee 2017-04-04 06:17:50 UTC Status POST MODIFIED
Atin Mukherjee 2017-04-06 01:57:33 UTC Fixed In Version glusterfs-3.8.4-21
errata-xmlrpc 2017-04-06 01:59:59 UTC Status MODIFIED ON_QA
Nag Pavan Chilakam 2017-04-11 09:20:36 UTC QA Contact nchilaka storage-qa-internal
Nag Pavan Chilakam 2017-04-26 14:18:06 UTC CC nchilaka
QA Contact storage-qa-internal rhinduja
Sweta Anandpara 2017-05-03 07:01:31 UTC CC sanandpa
QA Contact rhinduja sanandpa
Sweta Anandpara 2017-05-03 10:49:44 UTC Status ON_QA VERIFIED
hari gowtham 2017-06-06 12:00:47 UTC Doc Text Cause: During the reset of low watermarks we didn't have the check to verify if the low watermark being reset was higher than the high watermark. and vice versa.

Consequence: we were able to set low watermark higher than high watermark and hi watermark lower than low watermark.

Fix: put to check to avoid this happening.

Result: we won't be able to mess up with the wrong values in watermark by the watermark reset.
errata-xmlrpc 2017-09-21 00:53:22 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2017-09-21 04:25:52 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2017-09-21 00:25:52 UTC

Back to bug 1315583