Back to bug 1370027

Who When What Removed Added
Soumya Koduri 2016-08-25 06:04:14 UTC CC jthottan, kkeithle, ndevos, sraj
RHEL Program Management 2016-08-25 07:50:17 UTC Keywords FutureFeature
Soumya Koduri 2016-08-25 12:11:55 UTC Status NEW ASSIGNED
Component nfs-ganesha common-ha
Assignee kkeithle skoduri
Atin Mukherjee 2016-08-29 09:10:59 UTC CC amukherj
Soumya Koduri 2016-10-06 07:11:02 UTC Blocks 1382258
Soumya Koduri 2016-10-06 07:11:33 UTC Blocks 1382258
Depends On 1382258
Soumya Koduri 2016-10-06 07:14:03 UTC Status ASSIGNED POST
Jiffin 2016-10-13 09:53:49 UTC Keywords Triaged
John Skeoch 2016-11-08 03:55:32 UTC CC sraj sashinde
John Skeoch 2016-11-08 03:57:23 UTC QA Contact sraj sashinde
Jiffin 2016-11-08 06:18:11 UTC CC sbhaloth
John Skeoch 2016-11-18 04:10:36 UTC CC sashinde mzywusko
John Skeoch 2016-11-18 04:14:27 UTC QA Contact sashinde mzywusko
Rejy M Cyriac 2016-11-18 08:09:32 UTC QA Contact mzywusko sbhaloth
Soumya Koduri 2017-02-14 06:23:43 UTC Blocks 1417138
Soumya Koduri 2017-02-14 06:25:23 UTC Blocks 1414410
Atin Mukherjee 2017-02-20 11:45:11 UTC Version unspecified 3.3
Alok 2017-02-28 06:05:24 UTC CC asrivast
Rahul Hinduja 2017-03-06 07:00:48 UTC CC rhinduja
Red Hat Bugzilla Rules Engine 2017-03-06 13:12:37 UTC Target Release --- RHGS 3.3.0
Atin Mukherjee 2017-03-24 08:39:31 UTC Status POST MODIFIED
errata-xmlrpc 2017-03-30 21:16:52 UTC Status MODIFIED ON_QA
Milind Changire 2017-03-30 21:44:22 UTC Fixed In Version glusterfs-3.8.4-19
Jiffin 2017-04-19 10:22:30 UTC Depends On 1443478
Manisha Saini 2017-04-26 12:32:46 UTC Status ON_QA VERIFIED
CC msaini
QA Contact sbhaloth msaini
Soumya Koduri 2017-07-13 06:23:34 UTC Doc Text Cause: While setting up NFS-Ganesha cluster, pcsd service first tries to destroy existing cluster (if any present) which results in pacemaker service getting disabled.

Consequence: Post any node reboot, pacemaker service doesn't get started automatically.

Fix: With the fix now pacemaker service is explicitly re-enabled post successful NFS-Ganesha setup creation

Result: Pacemaker service gets started automatically now post any node reboot.
Doc Type If docs needed, set a value Bug Fix
Soumya Koduri 2017-07-13 06:27:13 UTC Doc Text Cause: While setting up NFS-Ganesha cluster, pcsd service first tries to destroy existing cluster (if any present) which results in pacemaker service getting disabled.

Consequence: Post any node reboot, pacemaker service doesn't get started automatically.

Fix: With the fix now pacemaker service is explicitly re-enabled post successful NFS-Ganesha setup creation

Result: Pacemaker service gets started automatically now post any node reboot.
Cause: To update the export configuration of any volume exported via NFS-Ganesha, the volume had to unexported and re-exported.

Consequence: This affects any on-going I/Os on the client for that period.

Fix: With this enhancement, now most of the export configuration options can be updated dynamically without the need to re-export the volume.

Result: The client work-loads shall not be affected during the period of this admin operation.
Doc Type Bug Fix Enhancement
Laura Bailey 2017-08-15 06:39:05 UTC CC skoduri
Doc Text Cause: To update the export configuration of any volume exported via NFS-Ganesha, the volume had to unexported and re-exported.

Consequence: This affects any on-going I/Os on the client for that period.

Fix: With this enhancement, now most of the export configuration options can be updated dynamically without the need to re-export the volume.

Result: The client work-loads shall not be affected during the period of this admin operation.
Most NFS-Ganesha export configuration options can now be updated dynamically during normal operation without needing to unexport and re-export the volume.
Flags needinfo?(skoduri)
Soumya Koduri 2017-08-16 08:43:19 UTC Flags needinfo?(skoduri)
errata-xmlrpc 2017-09-21 00:54:16 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2017-09-21 04:28:23 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2017-09-21 00:28:23 UTC

Back to bug 1370027