|Summary:||Introduce API support for requesting mandatory locks|
|Product:||[Community] GlusterFS||Reporter:||Anoop C S <anoopcs>|
|Component:||libgfapi||Assignee:||Anoop C S <anoopcs>|
|Status:||CLOSED EOL||QA Contact:||Sudhir D <sdharane>|
|Version:||3.8||CC:||bugs, ndevos, sdharane|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2017-11-07 10:40:31 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:||1346010|
Description Anoop C S 2016-06-13 16:29:17 UTC
+++ This bug was initially created as a clone of Bug #1346010 +++ Description of problem: In spite of having the mandatory-locks feature for GlusterFS, its native C API lacks support for requesting the same. This bug is to track the implementation/extension of libgfapi to provide this support for applications. Version-Release number of selected component (if applicable): mainline
Comment 1 Niels de Vos 2016-09-12 05:39:41 UTC
All 3.8.x bugs are now reported against version 3.8 (without .x). For more information, see http://www.gluster.org/pipermail/gluster-devel/2016-September/050859.html
Comment 2 Niels de Vos 2016-11-23 15:28:52 UTC
This bug did not make it in the glusterfs-3.8.6 release and has been moved to the 3.8.7 planning.
Comment 3 Niels de Vos 2016-12-11 16:26:05 UTC
This bug did not make it in the glusterfs-3.8.7 release and has been moved to the 3.8.8 planning.
Comment 4 Niels de Vos 2017-01-11 11:43:06 UTC
This bug did not make it in the glusterfs-3.8.8 release and has been moved to the 3.8.9 planning.
Comment 5 Niels de Vos 2017-02-13 08:44:51 UTC
This bug did not make it in the glusterfs-3.8.9 release and has been moved to the 3.8.10 planning.
Comment 6 Niels de Vos 2017-11-07 10:40:31 UTC
This bug is getting closed because the 3.8 version is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.