Back to bug 1024725
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| RamaKasturi | 2013-10-30 10:37:01 UTC | Severity | unspecified | high |
| Dusmant | 2013-10-30 11:08:51 UTC | Keywords | ZStream | |
| Priority | unspecified | high | ||
| CC | dpati | |||
| Vivek Agarwal | 2013-11-26 06:56:50 UTC | Status | NEW | ASSIGNED |
| CC | vagarwal | |||
| Assignee | rhs-bugs | kaushal | ||
| Krutika Dhananjay | 2013-11-28 10:24:34 UTC | Status | ASSIGNED | ON_QA |
| CC | kdhananj | |||
| Fixed In Version | glusterfs-3.4.0.44.1u2rhs | |||
| RamaKasturi | 2013-12-03 13:05:23 UTC | Status | ON_QA | ASSIGNED |
| Sudhir D | 2013-12-04 05:27:16 UTC | QA Contact | sdharane | knarra |
| Dusmant | 2013-12-06 09:31:25 UTC | Assignee | kaushal | kdhananj |
| Krutika Dhananjay | 2013-12-11 10:16:21 UTC | Blocks | 1040371 | |
| Krutika Dhananjay | 2013-12-16 11:28:03 UTC | Status | ASSIGNED | POST |
| Krutika Dhananjay | 2013-12-17 05:06:46 UTC | Status | POST | MODIFIED |
| Krutika Dhananjay | 2013-12-17 05:21:50 UTC | Status | MODIFIED | ON_QA |
| Fixed In Version | glusterfs-3.4.0.44.1u2rhs | glusterfs-3.4.0.50rhs-1 | ||
| RamaKasturi | 2013-12-19 05:08:48 UTC | Status | ON_QA | VERIFIED |
| Krutika Dhananjay | 2014-01-02 04:03:41 UTC | Doc Text | Cause: Previously, the stale status from a previous remove-brick/rebalance was not being reset before starting a new remove-brick/rebalance operation. Consequence: Because of this, remove-brick status used to give the output of a previous rebalance run, on those nodes which did not participate in the ongoing remove-brick task. Fix: The fix is to reset the remove-brick/rebalance status to NOT-STARTED just before starting a new defrag task on all the nodes in the cluster. Result: Now, remove-brick status no longer shows the status of a previous run of rebalance task. |
|
| Pavithra | 2014-01-07 07:02:54 UTC | CC | psriniva | |
| Doc Text | Cause: Previously, the stale status from a previous remove-brick/rebalance was not being reset before starting a new remove-brick/rebalance operation. Consequence: Because of this, remove-brick status used to give the output of a previous rebalance run, on those nodes which did not participate in the ongoing remove-brick task. Fix: The fix is to reset the remove-brick/rebalance status to NOT-STARTED just before starting a new defrag task on all the nodes in the cluster. Result: Now, remove-brick status no longer shows the status of a previous run of rebalance task. | Previously, status from a previous remove-brick or Rebalance operation was not reset before starting a new remove-brick or Rebalance operation. As a result, remove-brick status displayed the output of a previous Rebalance operation on those nodes which did not participate in an ongoing remove-brick operation. With this update, the status of the remove-brick or Rebalance operation is set to NOT-STARTED before starting remove-brick or Rebalance operations again on all the nodes in the cluster. | ||
| Flags | needinfo?(kdhananj) | |||
| Krutika Dhananjay | 2014-01-07 07:05:17 UTC | Flags | needinfo?(kdhananj) | |
| Jay Turner | 2014-01-15 11:25:11 UTC | Target Milestone | --- | RHS 2.1.2 |
| errata-xmlrpc | 2014-02-25 05:30:32 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2014-02-25 07:58:03 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2014-02-25 02:58:03 UTC | |||
| Rejy M Cyriac | 2015-05-13 16:26:38 UTC | Target Release | --- | RHGS 2.1.2 |
| Target Milestone | RHS 2.1.2 | --- |
Back to bug 1024725