Back to bug 1294612
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla Rules Engine | 2015-12-29 09:35:06 UTC | Keywords | ZStream | |
| Ravishankar N | 2015-12-29 09:35:32 UTC | Assignee | pkarampu | ravishankar |
| Ravishankar N | 2016-01-27 12:17:42 UTC | Blocks | 1302291 | |
| Pranith Kumar K | 2016-01-28 07:32:09 UTC | CC | pkarampu | |
| Pranith Kumar K | 2016-01-28 07:33:18 UTC | Status | NEW | POST |
| Ravishankar N | 2016-02-12 08:26:32 UTC | Blocks | 1306922 | |
| John Skeoch | 2016-02-18 00:11:21 UTC | CC | vagarwal | sankarshan |
| Rejy M Cyriac | 2016-02-19 16:54:52 UTC | Blocks | 1299184 | |
| Rahul Hinduja | 2016-03-01 10:26:28 UTC | CC | rhinduja | |
| Rejy M Cyriac | 2016-03-08 07:57:49 UTC | CC | rcyriac | |
| Red Hat Bugzilla Rules Engine | 2016-03-08 08:16:05 UTC | Target Release | --- | RHGS 3.1.3 |
| Nag Pavan Chilakam | 2016-03-15 11:34:56 UTC | CC | nchilaka | |
| Ravishankar N | 2016-03-24 04:21:12 UTC | Status | POST | MODIFIED |
| errata-xmlrpc | 2016-03-24 13:15:42 UTC | Status | MODIFIED | ON_QA |
| Satish Mohan | 2016-03-24 16:08:35 UTC | Fixed In Version | glusterfs-3.7.9-1 | |
| Rahul Hinduja | 2016-03-27 14:57:50 UTC | QA Contact | storage-qa-internal | nchilaka |
| Nag Pavan Chilakam | 2016-05-02 13:18:20 UTC | Status | ON_QA | VERIFIED |
| Ravishankar N | 2016-05-04 11:00:41 UTC | Doc Text | Previously, when launching index heal via the CLI, if some bricks were down, we would get the message "Launching heal operation to perform index self heal on volume vol0 has been unsuccessful". This could be confusing to the user because if there is atleast one source and one sink brick available for that file, the heal would indeed happen. With the fix, the message has been modified to make it more meaningful like so: "Launching heal operation to perform index self heal on volume vol0 has not been been successful on all nodes. Please check if all brick processes are running." | |
| Laura Bailey | 2016-06-09 03:51:38 UTC | CC | ravishankar | |
| Doc Text | Previously, when launching index heal via the CLI, if some bricks were down, we would get the message "Launching heal operation to perform index self heal on volume vol0 has been unsuccessful". This could be confusing to the user because if there is atleast one source and one sink brick available for that file, the heal would indeed happen. With the fix, the message has been modified to make it more meaningful like so: "Launching heal operation to perform index self heal on volume vol0 has not been been successful on all nodes. Please check if all brick processes are running." | Previously, if any bricks were down when an index heal was started, the following message was displayed: "Launching heal operation to perform index self heal on volume vol0 has been unsuccessful". This was confusing to users because the heal could still succeed if at least one source and one sink brick were available. The message has been modified to avoid confusion, and now reads: "Launching heal operation to perform index self heal on volume vol0 has not been been successful on all nodes. Please check if all brick processes are running." | ||
| Flags | needinfo?(ravishankar) | |||
| Ravishankar N | 2016-06-09 04:50:40 UTC | Flags | needinfo?(ravishankar) | |
| errata-xmlrpc | 2016-06-23 00:46:29 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-06-23 05:00:41 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-06-23 01:00:41 UTC | |||
| Rejy M Cyriac | 2016-09-17 12:19:03 UTC | CC | rhs-bugs, storage-qa-internal | |
| Component | gluster-afr | replicate |
Back to bug 1294612