Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: LTM release targeted for end of May

[Aravinda]

On 03/22/2018 11:34 PM, Shyam Ranganathan wrote:

On 03/21/2018 04:12 AM, Amar Tumballi wrote:

 Current 4.1 project release lane is empty! I cleaned it up, because I
 want to hear from all as to what content to add, than add things marked
 with the 4.1 milestone by default.


I would like to see we have sane default values for most of the options,
or have group options for many use-cases.

Amar, do we have an issue that lists the use-cases and hence the default
groups to be provided for the same?


Also want to propose that,  we include a release
of http://github.com/gluster/gluster-health-report with 4.1, and make
the project more usable.

In the theme of including sub-projects that we want to highlight, what
else should we tag a release for or highlight with 4.1?

@Aravinda, how do you envision releasing this with 4.1? IOW, what
interop tests and hence sanity can be ensured with 4.1 and how can we
tag a release that is sane against 4.1?


Some more changes required to make it work with Gluster 4.x, I will work 
on fixing those issues and test scripts.


I have not yet started with Packaging for Fedora/Ubuntu. As of now 
available as `pip install`. Let me know if that is fine with 4.1 release.





Also, we see that some of the patches from FB branch on namespace and
throttling are in, so we would like to call that feature out as
experimental by then.

I would assume we track this against
https://github.com/gluster/glusterfs/issues/408 would that be right?
___
maintainers mailing list
maintain...@gluster.org
http://lists.gluster.org/mailman/listinfo/maintainers



--
regards
Aravinda VK

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] ./tests/basic/md-cache/bug-1418249.t failing

[Susant Palai]

Sent a patch here - https://review.gluster.org/#/c/19768/ .

On Mon, Mar 26, 2018 at 7:50 AM, Susant Palai  wrote:

> Hi Poornima,
> As https://review.gluster.org/#/c/19744/ got merged, the $subject
> test case is failing on master.
> The "network.inode-lru-limit" is expecting the old "5" vs the current
> "20".
>
> Requesting to fix it.
>
>
> Susant
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] ./tests/basic/md-cache/bug-1418249.t failing

[Susant Palai]

Hi Poornima,
As https://review.gluster.org/#/c/19744/ got merged, the $subject test
case is failing on master.
The "network.inode-lru-limit" is expecting the old "5" vs the current
"20".

Requesting to fix it.


Susant
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Weekly Untriaged Bugs

[jenkins]

[...truncated 6 lines...]
https://bugzilla.redhat.com/1554718 / cli: error log daily
https://bugzilla.redhat.com/1558964 / core: 0kb files showing in glusterfs 
client
https://bugzilla.redhat.com/1549996 / core: [BMux] : Stale brick processes on 
the nodes after vol deletion.
https://bugzilla.redhat.com/1558574 / core: Coverity: Warning for singlton 
array..
https://bugzilla.redhat.com/1559075 / core: enable ownthread feature for 
glusterfs4_0_fop_prog
https://bugzilla.redhat.com/1552228 / core: Gluster brick process dies during 
rebalance
https://bugzilla.redhat.com/1555154 / core: glusterd: TLS verification fails 
when using intermediate CA instead of self-signed certificates
https://bugzilla.redhat.com/1559337 / core: server-less glusterfsd segmentation 
faults without volfile-id
https://bugzilla.redhat.com/1554732 / disperse: I can'nt get heal my gluster
https://bugzilla.redhat.com/1557435 / distribute: Enable lookup-optimize by 
default
https://bugzilla.redhat.com/1553543 / glusterd: Glusterfs-3.12.5 does not 
support kernel-4.14.14 and cannot start glusterfs.
https://bugzilla.redhat.com/1559130 / glusterfind: ssh stderr in glusterfind 
gets swallowed
https://bugzilla.redhat.com/1553777 / index: 
/var/log/glusterfs/bricks/export_vdb.log flooded with this error message "Not 
able to add to index [Too many links]"
https://bugzilla.redhat.com/1559004 / index: 
/var/log/glusterfs/bricks/export_vdb.log flooded with this error message "Not 
able to add to index [Too many links]"
https://bugzilla.redhat.com/1555315 / project-infrastructure: ansible role to 
deploy jenkins_builder sometime fail
https://bugzilla.redhat.com/1558320 / project-infrastructure: Freebsd smoke 
fails due to disk full
https://bugzilla.redhat.com/1557127 / project-infrastructure: github issue 
update on spec commits
https://bugzilla.redhat.com/1558335 / project-infrastructure: gluster-block: 
discontinue gerrit
https://bugzilla.redhat.com/1549662 / project-infrastructure: infra: create 
nfs-ganesha@ and nfs-ganesha-devel@
https://bugzilla.redhat.com/1551513 / project-infrastructure: Need merge rights 
for gdeploy repository on github
https://bugzilla.redhat.com/1550941 / rpc: [brick-mux] performance bottleneck 
introduced while solving ping timer expiry
https://bugzilla.redhat.com/1550946 / rpc: [brick-mux] performance bottleneck 
introduced while solving ping timer expiry
https://bugzilla.redhat.com/1548953 / rpc: Client keeps trying to connect to 
removed brick
https://bugzilla.redhat.com/1558380 / selfheal: Modify glfsheal binary to 
accept socket file path as an optional argument.
https://bugzilla.redhat.com/1559794 / tests: weighted-rebalance
https://bugzilla.redhat.com/1549714 / tiering: On sharded tiered volume, only 
first shard of new file goes on hot tier.
https://bugzilla.redhat.com/1558507 / unclassified: Gluster allows renaming of 
folders, which contain WORMed/Retain or WORMed files
https://bugzilla.redhat.com/1554286 / unclassified: Xattr not updated if 
increasing the retention of a WORM/Retained file
[...truncated 2 lines...]

build.log
Description: Binary data
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel