[Gluster-devel] Fwd: Status of 3.4 alpha/beta bugs

[John Mark Walker]

Forwarding to gluster-devel. We're aiming for an alpha3 release "ASAP".

Stay tuned for more info on 3.3.2-qa releases, coming up Real Soon Now.

-JM


----- Forwarded Message -----
From: "Jeff Darcy" <address@hidden>
Sent: Friday, April 12, 2013 8:39:14 AM
Subject: Re: Status of 3.4 alpha/beta bugs

> Here are the bugs associated with the 3.4beta1 tracker (918917).  I'm
> asking for three actions from each of you.
> 
> (1) If a bug is assigned to you, please verify its status.  POST means a
> patch has been posted, MODIFIED means the patch has been merged in
> master, ON_DEV means it has been merged in the release-3.4 branch,
> nothing should be ON_QA until it's actually in a tagged and published
> RPM.  Downstream status is irrelevant.
> 
> (2) If you think a bug is in the wrong category, let me know.
> 
> (3) If you know of other bugs that should be on one of these lists, let
> me know.
> 
> Once I'm sure the lists are correct, I'll create a separate 3.4alpha3
> tracker for those bugs, and track down all of the patches associated
> with each bug on the first two lists.  Thanks for all of your help.

List below has been updated to reflect last night's flurry of merges,
and to remove the list of updates that are already in the 3.4 branch.
Please pay particular attention to the list of patches needing backports
to 3.4alpha3, since there's not much of "this week" left.

Kudos to Shishir in particular for getting a bunch of bugs (some not
even his own IIRC) off these lists.


*** Need fix/backport for alpha3 (this week)

847214 (address@hidden)
glusterd operations hang if the other peers are down

924215 (address@hidden)
glusterd crashes when rdma.so not present

927146 (address@hidden)
AFR changelog vs data ordering is not durable

948686 (address@hidden)
Glusterd updates list of volumes and peers in a race'y manner.

950048 (address@hidden)
"gluster volume sync" command not working as expected



*** Need fix/backport for beta1 (before Summit)

762989 (address@hidden)
Possibility of GlusterFS port clashes with reserved ports

764924 (address@hidden)
Instability and High Server Memory Usage When Using RDMA Transport

765051 (address@hidden)
Use librdmacm for connection establishment.

794699 (address@hidden)
Can not tollerate failiure of a brick in replica volume

839810 (address@hidden)
RDMA high cpu usage and poor performance

887301 (address@hidden)
Container listing of objects is sorted resulting is higher latency in
response time

913544 (address@hidden)
stub unwind of ftruncate leads to crash

916372 (address@hidden)
NFS3 stable writes are very slow

919352 (address@hidden)
glusterd segfaults/core dumps on "gluster volume status ... detail"

919990 (address@hidden)
Crash in server_rpc_notify

928341 (address@hidden)
Enable write-behind for gluster nfs server process

950056 (address@hidden)
nfs.rpc-auth-allow does not work as expected with FQDN