Back to bug 1403767
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Atin Mukherjee | 2016-12-12 16:06:39 UTC | CC | msaini | |
| Flags | needinfo?(msaini) | |||
| SATHEESARAN | 2016-12-12 16:24:34 UTC | CC | sasundar | |
| Byreddy | 2016-12-13 04:29:37 UTC | CC | bsrirama | |
| Manisha Saini | 2016-12-13 07:32:01 UTC | Flags | needinfo?(msaini) | |
| Rahul Hinduja | 2016-12-14 14:35:48 UTC | CC | rhinduja | |
| Blocks | 1351530 | |||
| Atin Mukherjee | 2017-02-02 14:44:16 UTC | Doc Type | If docs needed, set a value | Known Issue |
| Atin Mukherjee | 2017-02-02 14:44:41 UTC | Assignee | amukherj | sbairagy |
| Atin Mukherjee | 2017-03-06 03:54:27 UTC | CC | amukherj | |
| Doc Text | Problem: On a multi node setup where Ganesha is configured, if the setup has multiple volumes, if a node is rebooted and at the same time if a volume is stopped, once the node comes up the volume status shows that volume is in started state where as it should have been stopped. Workaround (if any): Restarting GlusterD instance on the node where the volume status reflects "started" solves the issue. Result: |
|||
| Bhavana | 2017-03-13 15:57:46 UTC | CC | bmohanra | |
| Doc Text | Problem: On a multi node setup where Ganesha is configured, if the setup has multiple volumes, if a node is rebooted and at the same time if a volume is stopped, once the node comes up the volume status shows that volume is in started state where as it should have been stopped. Workaround (if any): Restarting GlusterD instance on the node where the volume status reflects "started" solves the issue. Result: | On a multi node setup where NFS-Ganesha is configured, if the setup has multiple volumes and a node is rebooted at the same time as when volume is stopped, then, once the node comes up the volume status shows that volume is in started state where as it should have been stopped. Workaround Restarting the GlusterD instance on the node where the volume status reflects "started" resolves the issue. |
||
| Red Hat Bugzilla Rules Engine | 2017-06-28 09:09:32 UTC | Keywords | ZStream | |
| PnT Account Manager | 2018-01-29 21:28:38 UTC | CC | bsrirama | |
| Atin Mukherjee | 2018-04-01 13:28:51 UTC | Flags | needinfo?(msaini) | |
| PnT Account Manager | 2018-05-25 21:30:31 UTC | Assignee | sbairagy | amukherj |
| Atin Mukherjee | 2018-08-20 04:07:53 UTC | Flags | needinfo?(msaini) | |
| Nag Pavan Chilakam | 2018-10-24 08:18:46 UTC | CC | nchilaka | |
| Severity | unspecified | high | ||
| Jilju Joy | 2018-10-31 08:33:20 UTC | CC | jijoy | |
| Flags | needinfo?(msaini) needinfo?(msaini) | |||
| Atin Mukherjee | 2018-10-31 08:43:54 UTC | Status | NEW | CLOSED |
| Blocks | 1351530 | |||
| Resolution | --- | CURRENTRELEASE | ||
| Doc Type | Known Issue | If docs needed, set a value | ||
| Last Closed | 2018-10-31 04:43:54 UTC | |||
| Laura Bailey | 2019-10-16 03:54:00 UTC | Doc Text | On a multi node setup where NFS-Ganesha is configured, if the setup has multiple volumes and a node is rebooted at the same time as when volume is stopped, then, once the node comes up the volume status shows that volume is in started state where as it should have been stopped. Workaround Restarting the GlusterD instance on the node where the volume status reflects "started" resolves the issue. | In multi-node NFS-Ganesha configurations with multiple volumes, if a node was rebooted while a volume was stopped, volume status was reported incorrectly. This is resolved as of Red Hat Gluster Storage 3.4. |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Flags | needinfo?(amukherj) | |||
| Atin Mukherjee | 2019-10-16 06:34:01 UTC | CC | asriram | |
| Flags | needinfo?(amukherj) | needinfo?(asriram) |
Back to bug 1403767