Back to bug 1398280
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Soumya Koduri | 2016-11-24 12:32:13 UTC | CC | aloganat | |
| Flags | needinfo?(aloganat) | |||
| Arthy Loganathan | 2016-11-25 06:48:48 UTC | Flags | needinfo?(aloganat) | |
| Soumya Koduri | 2016-11-25 10:17:53 UTC | Flags | needinfo?(aloganat) | |
| Arthy Loganathan | 2016-11-28 06:32:36 UTC | Flags | needinfo?(aloganat) | |
| Atin Mukherjee | 2016-11-28 07:50:39 UTC | CC | amukherj | |
| Atin Mukherjee | 2016-11-28 07:51:27 UTC | Blocks | 1351530 | |
| Atin Mukherjee | 2017-02-02 14:41:31 UTC | Doc Type | If docs needed, set a value | Known Issue |
| Jiffin | 2017-03-09 09:09:17 UTC | Doc Text | Cause: If any one of the pcs resources in failed state, then teardown requires a lot of time to complete Consequence: The command gluster nfs-ganesha disable will timeout Workaround (if any): If gluster nfs-ganesha disable errored with timeout, perform the pcs status and check whether any resource in failed state. Then perform cleanup for that resource using following command pcs resource --cleanup <resource id> And rerun the gluster nfs-ganesha disable Result: HA cluster and ganesha process won't clean up properly |
|
| Bhavana | 2017-03-13 06:36:04 UTC | CC | bmohanra | |
| Doc Text | Cause: If any one of the pcs resources in failed state, then teardown requires a lot of time to complete Consequence: The command gluster nfs-ganesha disable will timeout Workaround (if any): If gluster nfs-ganesha disable errored with timeout, perform the pcs status and check whether any resource in failed state. Then perform cleanup for that resource using following command pcs resource --cleanup <resource id> And rerun the gluster nfs-ganesha disable Result: HA cluster and ganesha process won't clean up properly | If any of the PCS resources are in the failed state, then the teardown requires a lot of time to complete. Due to this, the command "gluster nfs-ganesha disable" will timeout. Workaround: If "gluster nfs-ganesha disable" errored with a timeout, then perform the pcs status and check whether any resource is in failed state. Then perform cleanup for that resource using following command pcs resource --cleanup <resource id> Re-execute the "gluster nfs-ganesha disable" command. |
||
| Red Hat Bugzilla Rules Engine | 2017-06-28 09:06:30 UTC | Keywords | ZStream | |
| Kaleb KEITHLEY | 2017-08-23 12:33:36 UTC | Status | NEW | ASSIGNED |
| Soumya Koduri | 2017-08-23 12:37:12 UTC | Component | nfs-ganesha | common-ha |
| PnT Account Manager | 2018-02-14 21:38:07 UTC | QA Contact | aloganat | msaini |
| PnT Account Manager | 2018-02-14 21:38:51 UTC | CC | aloganat | |
| Pasi Karkkainen | 2018-11-19 10:02:20 UTC | CC | pasik | |
| Arjun | 2019-05-13 11:40:43 UTC | Keywords | Triaged | |
| CC | arjsharm | |||
| Jiffin | 2019-05-20 12:40:42 UTC | Status | ASSIGNED | CLOSED |
| Resolution | --- | WONTFIX | ||
| Last Closed | 2019-05-20 12:40:42 UTC |
Back to bug 1398280