Back to bug 1306667
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla Rules Engine | 2016-02-11 14:41:38 UTC | Keywords | ZStream | |
| Byreddy | 2016-02-11 15:07:08 UTC | Version | unspecified | 3.1 |
| Atin Mukherjee | 2016-02-11 15:59:00 UTC | Assignee | amukherj | ggarg |
| Atin Mukherjee | 2016-02-11 16:05:37 UTC | CC | amukherj | |
| Byreddy | 2016-02-12 05:29:11 UTC | Keywords | Regression | |
| Rejy M Cyriac | 2016-02-12 06:39:33 UTC | CC | rcyriac | |
| Atin Mukherjee | 2016-02-12 07:15:14 UTC | Status | NEW | ASSIGNED |
| Nag Pavan Chilakam | 2016-02-12 16:51:31 UTC | Blocks | 1268895 | |
| Atin Mukherjee | 2016-02-12 17:01:36 UTC | Doc Text | If server side quorum is not met, executing gluster volume start <volname> will start the volume where it should have failed since the quorum is not met. | |
| Doc Type | Bug Fix | Known Issue | ||
| Laura Bailey | 2016-02-15 02:54:03 UTC | Doc Text | If server side quorum is not met, executing gluster volume start <volname> will start the volume where it should have failed since the quorum is not met. | If server-side quorum is enabled, and the quorum conditions are not met, starting a volume should fail. However, executing 'gluster volume start' succeeds even when quorum conditions are not met. |
| Laura Bailey | 2016-02-15 02:55:02 UTC | Flags | needinfo?(amukherj) | |
| Atin Mukherjee | 2016-02-15 04:27:37 UTC | Flags | needinfo?(amukherj) | |
| Gaurav Kumar Garg | 2016-02-15 05:17:32 UTC | Blocks | 1308402 | |
| Gaurav Kumar Garg | 2016-02-15 05:23:42 UTC | Status | ASSIGNED | POST |
| Atin Mukherjee | 2016-02-15 05:46:55 UTC | Doc Text | If server-side quorum is enabled, and the quorum conditions are not met, starting a volume should fail. However, executing 'gluster volume start' succeeds even when quorum conditions are not met. | If server-side quorum is enabled, and the quorum conditions are not met, starting a volume should fail. However, executing 'gluster volume start' succeeds even when quorum conditions are not met. Workaround: 1. Disable server side quorum by gluster volume reset <volname> cluster.server-quorum-type 2. Stop the volume 3. Turn on server side quorum by gluster volume set <volname> cluster.server-quorum-type server |
| Laura Bailey | 2016-02-15 06:15:05 UTC | Doc Text | If server-side quorum is enabled, and the quorum conditions are not met, starting a volume should fail. However, executing 'gluster volume start' succeeds even when quorum conditions are not met. Workaround: 1. Disable server side quorum by gluster volume reset <volname> cluster.server-quorum-type 2. Stop the volume 3. Turn on server side quorum by gluster volume set <volname> cluster.server-quorum-type server | If server-side quorum is enabled, and the quorum conditions are not met, starting a volume should fail. However, executing 'gluster volume start' succeeds even when quorum conditions are not met. Workaround: 1. Disable server-side quorum: # gluster volume reset $volname cluster.server-quorum-type 2. Stop the volume. 3. Re-enable server-side quorum. # gluster volume set $volname cluster.server-quorum-type server |
| Flags | needinfo?(amukherj) | |||
| Laura Bailey | 2016-02-15 06:28:36 UTC | Doc Text | If server-side quorum is enabled, and the quorum conditions are not met, starting a volume should fail. However, executing 'gluster volume start' succeeds even when quorum conditions are not met. Workaround: 1. Disable server-side quorum: # gluster volume reset $volname cluster.server-quorum-type 2. Stop the volume. 3. Re-enable server-side quorum. # gluster volume set $volname cluster.server-quorum-type server | If server-side quorum is enabled, and the quorum conditions are not met, starting a volume should fail. Currently, executing 'gluster volume start' incorrectly succeeds even when quorum conditions are not met. However, because stopping the volume is correctly dependent on quorum conditions being met, this means that attempts to stop the volume fail while quorum is enabled. Workaround: 1. Disable server-side quorum: # gluster volume reset $volname cluster.server-quorum-type 2. Stop the volume. 3. Re-enable server-side quorum. # gluster volume set $volname cluster.server-quorum-type server |
| Atin Mukherjee | 2016-02-15 06:38:59 UTC | Flags | needinfo?(amukherj) | |
| Rejy M Cyriac | 2016-02-19 16:53:02 UTC | Blocks | 1299184 | |
| Gaurav Kumar Garg | 2016-02-22 12:02:53 UTC | Blocks | 1310630 | |
| Gaurav Kumar Garg | 2016-02-22 12:03:12 UTC | Blocks | 1310631 | |
| Gaurav Kumar Garg | 2016-02-22 12:03:23 UTC | Blocks | 1310632 | |
| Gaurav Kumar Garg | 2016-02-22 12:04:03 UTC | Blocks | 1310632 | |
| Atin Mukherjee | 2016-02-23 08:48:24 UTC | QA Contact | storage-qa-internal | bsrirama |
| Gaurav Kumar Garg | 2016-02-23 12:18:25 UTC | Blocks | 1310631 | |
| Gaurav Kumar Garg | 2016-02-23 12:21:32 UTC | Blocks | 1310630 | |
| Rahul Hinduja | 2016-03-01 07:29:44 UTC | CC | rhinduja | |
| Alok | 2016-03-03 09:35:26 UTC | CC | asrivast | |
| Red Hat Bugzilla Rules Engine | 2016-03-08 08:16:47 UTC | Target Release | --- | RHGS 3.1.3 |
| Atin Mukherjee | 2016-03-22 11:58:08 UTC | Status | POST | MODIFIED |
| errata-xmlrpc | 2016-03-24 13:18:20 UTC | Status | MODIFIED | ON_QA |
| Satish Mohan | 2016-03-24 16:12:33 UTC | Fixed In Version | glusterfs-3.7.9-1 | |
| Byreddy | 2016-04-04 07:17:10 UTC | Status | ON_QA | VERIFIED |
| Atin Mukherjee | 2016-05-03 11:06:54 UTC | Doc Type | Known Issue | Bug Fix |
| Red Hat Bugzilla | 2016-05-03 11:06:54 UTC | Doc Type | Bug Fix | Known Issue |
| Atin Mukherjee | 2016-05-03 11:10:57 UTC | Doc Text | If server-side quorum is enabled, and the quorum conditions are not met, starting a volume should fail. Currently, executing 'gluster volume start' incorrectly succeeds even when quorum conditions are not met. However, because stopping the volume is correctly dependent on quorum conditions being met, this means that attempts to stop the volume fail while quorum is enabled. Workaround: 1. Disable server-side quorum: # gluster volume reset $volname cluster.server-quorum-type 2. Stop the volume. 3. Re-enable server-side quorum. # gluster volume set $volname cluster.server-quorum-type server | |
| Doc Type | Known Issue | Bug Fix | ||
| Gaurav Kumar Garg | 2016-05-04 10:15:42 UTC | Doc Text | Currently, When server quorum is not met then upon executing # gluster volume start [force] command its starting the volume. With this fix if server side quorum is not met then it will prevent starting of the volume. |
|
| John Skeoch | 2016-06-05 23:41:05 UTC | Assignee | ggarg | smohan |
| Laura Bailey | 2016-06-06 06:45:59 UTC | CC | smohan | |
| Doc Text | Currently, When server quorum is not met then upon executing # gluster volume start [force] command its starting the volume. With this fix if server side quorum is not met then it will prevent starting of the volume. | Previously, using the force option with the 'gluster volume start' command succeeded even when server-side quorum was not met. This has been corrected so that force no longer overrides a lack of server-side quorum being met. | ||
| Flags | needinfo?(smohan) | |||
| Atin Mukherjee | 2016-06-06 06:51:02 UTC | Assignee | smohan | amukherj |
| Laura Bailey | 2016-06-07 00:24:25 UTC | Flags | needinfo?(smohan) | |
| errata-xmlrpc | 2016-06-23 00:48:20 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-06-23 05:07:48 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-06-23 01:07:48 UTC | |||
| Rejy M Cyriac | 2016-09-17 16:32:48 UTC | Sub Component | glusterd | |
| Component | glusterd | glusterd-transition | ||
| Rejy M Cyriac | 2016-09-17 16:45:22 UTC | CC | rhs-bugs, storage-qa-internal, vbellur | |
| Component | glusterd-transition | glusterd |
Back to bug 1306667