[Gluster-devel] IMP: Release 3.10: RC1 Pending bugs (Need fixes by 21st Feb)
srangana at redhat.com
Tue Feb 21 12:17:10 UTC 2017
On 02/19/2017 09:55 PM, Shyam wrote:
> RC1 tagging is *tentatively* scheduled for 21st Feb, 2017
> The intention is that RC1 becomes the release, hence we would like to
> chase down all blocker bugs  and get them fixed before RC1 is tagged.
> This mail requests information on the various bugs and to understand if
> it is possible to get them fixed done by the 21st.
Here is an update on this list.
> Bugs pending for RC1 tagging:
> 1) Bug 1415226 - packaging: python/python2(/python3) cleanup
> 2) Bug 1421590 - Bricks take up new ports upon volume restart after
> add-brick op with brick mux enabled
> - Status: *Atin/Samikshan/Jeff*, any update on this?
> - Can we document this as a known issue? What would be the way to
> get volume to use the older ports (a glusterd restart?)?
Patch under review for master. Atin/Samikshan are we going to wait for
this be backported? The last update was we need not consider this a
blocker for the release, does that still hold?
> 3) Bug 1421956 - Disperse: Fallback to pre-compiled code execution
> when dynamic code generation fails
> 4) Bug 1422769 - brick process crashes when glusterd is restarted
Atin/Samikshan, thoughts on this?
> 5) Bug 1422781 - Transport endpoint not connected error seen on client
> when glusterd is restarted
> - Status: Repro not clean across setups, still debugging the problem
Atin/Samikshan, were we able to narrow this down, post attempts to
> 6) Bug 1423385 - Crash in index xlator because of race in
> inode_ctx_set and inode_ref
>  3.10 tracker bug:
>  Dynamic tracker list:
> Gluster-devel mailing list
> Gluster-devel at gluster.org
More information about the Gluster-devel