[Gluster-Maintainers] Build failed in Jenkins: regression-test-with-multiplex #1173

2019-02-26 Thread jenkins 
See 


--
[...truncated 1.03 MB...]
./tests/basic/mgmt_v3-locks.t  -  7 second
./tests/basic/glusterd/arbiter-volume-probe.t  -  7 second
./tests/basic/gfapi/mandatory-lock-optimal.t  -  7 second
./tests/basic/fop-sampling.t  -  7 second
./tests/basic/ec/ec-anonymous-fd.t  -  7 second
./tests/basic/distribute/file-create.t  -  7 second
./tests/basic/afr/ta-shd.t  -  7 second
./tests/basic/afr/tarissue.t  -  7 second
./tests/basic/afr/gfid-mismatch.t  -  7 second
./tests/gfid2path/get-gfid-to-path.t  -  6 second
./tests/gfid2path/block-mount-access.t  -  6 second
./tests/features/lock-migration/lkmigration-set-option.t  -  6 second
./tests/bugs/upcall/bug-1458127.t  -  6 second
./tests/bugs/snapshot/bug-1064768.t  -  6 second
./tests/bugs/replicate/bug-767585-gfid.t  -  6 second
./tests/bugs/replicate/bug-1498570-client-iot-graph-check.t  -  6 second
./tests/bugs/quota/bug-1250582-volume-reset-should-not-remove-quota-quota-deem-statfs.t
  -  6 second
./tests/bugs/quota/bug-1243798.t  -  6 second
./tests/bugs/posix/bug-990028.t  -  6 second
./tests/bugs/nfs/bug-915280.t  -  6 second
./tests/bugs/nfs/bug-1143880-fix-gNFSd-auth-crash.t  -  6 second
./tests/bugs/md-cache/setxattr-prepoststat.t  -  6 second
./tests/bugs/io-cache/bug-read-hang.t  -  6 second
./tests/bugs/io-cache/bug-858242.t  -  6 second
./tests/bugs/glusterfs-server/bug-904300.t  -  6 second
./tests/bugs/glusterfs/bug-861015-log.t  -  6 second
./tests/bugs/gfapi/bug-1630804/gfapi-bz1630804.t  -  6 second
./tests/bugs/gfapi/bug-1447266/1460514.t  -  6 second
./tests/bugs/ec/bug-1227869.t  -  6 second
./tests/bugs/distribute/bug-884597.t  -  6 second
./tests/bugs/distribute/bug-882278.t  -  6 second
./tests/bugs/distribute/bug-1088231.t  -  6 second
./tests/bugs/core/bug-986429.t  -  6 second
./tests/bugs/core/bug-908146.t  -  6 second
./tests/bugs/bug-1371806_2.t  -  6 second
./tests/bugs/bitrot/bug-1229134-bitd-not-support-vol-set.t  -  6 second
./tests/bugs/bitrot/1209751-bitrot-scrub-tunable-reset.t  -  6 second
./tests/bugs/bitrot/1207029-bitrot-daemon-should-start-on-valid-node.t  -  6 
second
./tests/basic/volume-status.t  -  6 second
./tests/basic/playground/template-xlator-sanity.t  -  6 second
./tests/basic/inode-quota-enforcing.t  -  6 second
./tests/basic/glusterd/arbiter-volume.t  -  6 second
./tests/basic/gfapi/upcall-cache-invalidate.t  -  6 second
./tests/basic/gfapi/glfs_xreaddirplus_r.t  -  6 second
./tests/basic/gfapi/anonymous_fd.t  -  6 second
./tests/basic/ec/nfs.t  -  6 second
./tests/basic/ec/ec-read-policy.t  -  6 second
./tests/basic/ctime/ctime-noatime.t  -  6 second
./tests/basic/afr/heal-info.t  -  6 second
./tests/basic/afr/gfid-heal.t  -  6 second
./tests/basic/afr/arbiter-remove-brick.t  -  6 second
./tests/features/flock_interrupt.t  -  5 second
./tests/bugs/upcall/bug-1369430.t  -  5 second
./tests/bugs/shard/bug-1468483.t  -  5 second
./tests/bugs/shard/bug-1342298.t  -  5 second
./tests/bugs/shard/bug-1258334.t  -  5 second
./tests/bugs/replicate/bug-1365455.t  -  5 second
./tests/bugs/replicate/bug-1250170-fsync.t  -  5 second
./tests/bugs/posix/bug-1034716.t  -  5 second
./tests/bugs/md-cache/bug-1211863_unlink.t  -  5 second
./tests/bugs/md-cache/afr-stale-read.t  -  5 second
./tests/bugs/io-stats/bug-1598548.t  -  5 second
./tests/bugs/glusterfs-server/bug-873549.t  -  5 second
./tests/bugs/glusterfs/bug-848251.t  -  5 second
./tests/bugs/glusterd/quorum-value-check.t  -  5 second
./tests/bugs/glusterd/bug-948729/bug-948729-force.t  -  5 second
./tests/bugs/fuse/bug-1030208.t  -  5 second
./tests/bugs/core/bug-834465.t  -  5 second
./tests/bugs/core/bug-1168803-snapd-option-validation-fix.t  -  5 second
./tests/bugs/bitrot/bug-1210684-scrub-pause-resume-error-handling.t  -  5 second
./tests/bitrot/bug-1221914.t  -  5 second
./tests/bitrot/br-stub.t  -  5 second
./tests/basic/posix/zero-fill-enospace.t  -  5 second
./tests/basic/gfapi/glfd-lkowner.t  -  5 second
./tests/basic/gfapi/gfapi-dup.t  -  5 second
./tests/basic/gfapi/bug-1241104.t  -  5 second
./tests/basic/fencing/fencing-crash-conistency.t  -  5 second
./tests/basic/fencing/fence-basic.t  -  5 second
./tests/basic/ec/ec-internal-xattrs.t  -  5 second
./tests/basic/ec/ec-fallocate.t  -  5 second
./tests/basic/ec/dht-rename.t  -  5 second
./tests/basic/distribute/throttle-rebal.t  -  5 second
./tests/basic/ctime/ctime-glfs-init.t  -  5 second
./tests/basic/changelog/changelog-rename.t  -  5 second
./tests/basic/afr/afr-read-hash-mode.t  -  5 second
./tests/performance/quick-read.t  -  4 second
./tests/features/readdir-ahead.t  -  4 second
./tests/bugs/upcall/bug-upcall-stat.t  -  4 second
./tests/bugs/unclassified/bug-1034085.t  -  4 second
./tests/bugs/transport/bug-873367.t  -  4 second
./tests/bugs/snapshot/bug-1178079.t  -  4 second
./tests/bugs/snapshot/bug-041.t  -  4 second
./tests/bugs/shard/bug-1272986.t  -  4

[Gluster-Maintainers] Build failed in Jenkins: regression-test-with-multiplex #1172

2019-02-26 Thread jenkins 
See 


Changes:

[Amar Tumballi] glusterfind: revert shebangs to #!/usr/bin/python3

[Amar Tumballi] build: do not install service related files when building

--
[...truncated 1.03 MB...]
./tests/bugs/gfapi/bug-1447266/1460514.t  -  7 second
./tests/bugs/fuse/bug-963678.t  -  7 second
./tests/bugs/ec/bug-1179050.t  -  7 second
./tests/bugs/distribute/bug-1122443.t  -  7 second
./tests/bugs/core/bug-949242.t  -  7 second
./tests/bugs/changelog/bug-1208470.t  -  7 second
./tests/bugs/bitrot/1209818-vol-info-show-scrub-process-properly.t  -  7 second
./tests/bugs/bitrot/1209752-volume-status-should-show-bitrot-scrub-info.t  -  7 
second
./tests/bugs/bitrot/1209751-bitrot-scrub-tunable-reset.t  -  7 second
./tests/basic/xlator-pass-through-sanity.t  -  7 second
./tests/basic/pgfid-feat.t  -  7 second
./tests/basic/inode-quota-enforcing.t  -  7 second
./tests/basic/fop-sampling.t  -  7 second
./tests/basic/afr/gfid-mismatch.t  -  7 second
./tests/gfid2path/block-mount-access.t  -  6 second
./tests/bugs/snapshot/bug-1064768.t  -  6 second
./tests/bugs/replicate/bug-1561129-enospc.t  -  6 second
./tests/bugs/replicate/bug-1498570-client-iot-graph-check.t  -  6 second
./tests/bugs/replicate/bug-1250170-fsync.t  -  6 second
./tests/bugs/quota/bug-1243798.t  -  6 second
./tests/bugs/nfs/bug-915280.t  -  6 second
./tests/bugs/nfs/bug-1143880-fix-gNFSd-auth-crash.t  -  6 second
./tests/bugs/md-cache/setxattr-prepoststat.t  -  6 second
./tests/bugs/io-cache/bug-858242.t  -  6 second
./tests/bugs/glusterfs-server/bug-904300.t  -  6 second
./tests/bugs/glusterfs/bug-861015-log.t  -  6 second
./tests/bugs/glusterd/quorum-value-check.t  -  6 second
./tests/bugs/gfapi/bug-1630804/gfapi-bz1630804.t  -  6 second
./tests/bugs/fuse/bug-985074.t  -  6 second
./tests/bugs/ec/bug-1227869.t  -  6 second
./tests/bugs/distribute/bug-884597.t  -  6 second
./tests/bugs/distribute/bug-882278.t  -  6 second
./tests/bugs/distribute/bug-1088231.t  -  6 second
./tests/bugs/core/bug-986429.t  -  6 second
./tests/bugs/bug-1258069.t  -  6 second
./tests/bugs/bitrot/1207029-bitrot-daemon-should-start-on-valid-node.t  -  6 
second
./tests/bitrot/bug-1221914.t  -  6 second
./tests/bitrot/br-stub.t  -  6 second
./tests/basic/volume-status.t  -  6 second
./tests/basic/playground/template-xlator-sanity.t  -  6 second
./tests/basic/glusterd/arbiter-volume-probe.t  -  6 second
./tests/basic/gfapi/gfapi-dup.t  -  6 second
./tests/basic/gfapi/bug-1241104.t  -  6 second
./tests/basic/ec/ec-read-policy.t  -  6 second
./tests/basic/ec/ec-fallocate.t  -  6 second
./tests/basic/distribute/file-create.t  -  6 second
./tests/basic/ctime/ctime-glfs-init.t  -  6 second
./tests/basic/afr/tarissue.t  -  6 second
./tests/basic/afr/gfid-heal.t  -  6 second
./tests/basic/afr/arbiter-remove-brick.t  -  6 second
./tests/features/flock_interrupt.t  -  5 second
./tests/bugs/upcall/bug-1369430.t  -  5 second
./tests/bugs/shard/bug-1468483.t  -  5 second
./tests/bugs/shard/bug-1342298.t  -  5 second
./tests/bugs/shard/bug-1258334.t  -  5 second
./tests/bugs/replicate/bug-767585-gfid.t  -  5 second
./tests/bugs/replicate/bug-1365455.t  -  5 second
./tests/bugs/replicate/bug-1101647.t  -  5 second
./tests/bugs/quota/bug-1104692.t  -  5 second
./tests/bugs/posix/bug-990028.t  -  5 second
./tests/bugs/posix/bug-1034716.t  -  5 second
./tests/bugs/nfs/bug-877885.t  -  5 second
./tests/bugs/glusterfs-server/bug-873549.t  -  5 second
./tests/bugs/glusterfs/bug-902610.t  -  5 second
./tests/bugs/glusterfs/bug-848251.t  -  5 second
./tests/bugs/fuse/bug-1030208.t  -  5 second
./tests/bugs/core/bug-908146.t  -  5 second
./tests/bugs/core/bug-834465.t  -  5 second
./tests/bugs/core/bug-1168803-snapd-option-validation-fix.t  -  5 second
./tests/bugs/bug-1371806_2.t  -  5 second
./tests/bugs/bitrot/bug-1229134-bitd-not-support-vol-set.t  -  5 second
./tests/bugs/bitrot/bug-1210684-scrub-pause-resume-error-handling.t  -  5 second
./tests/basic/posix/zero-fill-enospace.t  -  5 second
./tests/basic/glusterd/arbiter-volume.t  -  5 second
./tests/basic/gfapi/upcall-cache-invalidate.t  -  5 second
./tests/basic/gfapi/glfs_xreaddirplus_r.t  -  5 second
./tests/basic/gfapi/glfd-lkowner.t  -  5 second
./tests/basic/gfapi/anonymous_fd.t  -  5 second
./tests/basic/fencing/fencing-crash-conistency.t  -  5 second
./tests/basic/fencing/fence-basic.t  -  5 second
./tests/basic/ec/nfs.t  -  5 second
./tests/basic/ec/ec-internal-xattrs.t  -  5 second
./tests/basic/ec/dht-rename.t  -  5 second
./tests/basic/distribute/throttle-rebal.t  -  5 second
./tests/basic/ctime/ctime-noatime.t  -  5 second
./tests/basic/afr/heal-info.t  -  5 second
./tests/basic/afr/afr-read-hash-mode.t  -  5 second
./tests/performance/quick-read.t  -  4 second
./tests/bugs/upcall/bug-upcall-stat.t  -  4 second
./tests/bugs/unclassified/bug-1034085.t  -  4 second

[Gluster-Maintainers] Build failed in Jenkins: experimental-periodic #611

2019-02-26 Thread jenkins 
See 

--
[...truncated 974.64 KB...]
./tests/bugs/geo-replication/bug-877293.t  -  7 second
./tests/bugs/fuse/bug-963678.t  -  7 second
./tests/bugs/distribute/bug-882278.t  -  7 second
./tests/bugs/cli/bug-1087487.t  -  7 second
./tests/bugs/changelog/bug-1208470.t  -  7 second
./tests/basic/xlator-pass-through-sanity.t  -  7 second
./tests/basic/quota-nfs.t  -  7 second
./tests/basic/fop-sampling.t  -  7 second
./tests/basic/ec/ec-anonymous-fd.t  -  7 second
./tests/basic/afr/gfid-mismatch.t  -  7 second
./tests/gfid2path/get-gfid-to-path.t  -  6 second
./tests/features/lock-migration/lkmigration-set-option.t  -  6 second
./tests/bugs/upcall/bug-1458127.t  -  6 second
./tests/bugs/snapshot/bug-1260848.t  -  6 second
./tests/bugs/snapshot/bug-1064768.t  -  6 second
./tests/bugs/replicate/bug-921231.t  -  6 second
./tests/bugs/replicate/bug-1498570-client-iot-graph-check.t  -  6 second
./tests/bugs/replicate/bug-1132102.t  -  6 second
./tests/bugs/quota/bug-1243798.t  -  6 second
./tests/bugs/posix/bug-990028.t  -  6 second
./tests/bugs/glusterd/bug-1242875-do-not-pass-volinfo-quota.t  -  6 second
./tests/bugs/gfapi/bug-1630804/gfapi-bz1630804.t  -  6 second
./tests/bugs/gfapi/bug-1447266/1460514.t  -  6 second
./tests/bugs/fuse/bug-985074.t  -  6 second
./tests/bugs/ec/bug-1179050.t  -  6 second
./tests/bugs/distribute/bug-1368012.t  -  6 second
./tests/bugs/core/bug-986429.t  -  6 second
./tests/bugs/bitrot/1209818-vol-info-show-scrub-process-properly.t  -  6 second
./tests/bitrot/br-stub.t  -  6 second
./tests/basic/playground/template-xlator-sanity.t  -  6 second
./tests/basic/inode-quota-enforcing.t  -  6 second
./tests/basic/glusterd/arbiter-volume-probe.t  -  6 second
./tests/basic/gfapi/mandatory-lock-optimal.t  -  6 second
./tests/basic/gfapi/glfs_xreaddirplus_r.t  -  6 second
./tests/basic/gfapi/glfd-lkowner.t  -  6 second
./tests/basic/distribute/throttle-rebal.t  -  6 second
./tests/basic/distribute/file-create.t  -  6 second
./tests/basic/afr/heal-info.t  -  6 second
./tests/basic/afr/arbiter-remove-brick.t  -  6 second
./tests/gfid2path/block-mount-access.t  -  5 second
./tests/features/flock_interrupt.t  -  5 second
./tests/bugs/upcall/bug-1369430.t  -  5 second
./tests/bugs/shard/bug-1468483.t  -  5 second
./tests/bugs/replicate/bug-767585-gfid.t  -  5 second
./tests/bugs/replicate/bug-1365455.t  -  5 second
./tests/bugs/quota/bug-1250582-volume-reset-should-not-remove-quota-quota-deem-statfs.t
  -  5 second
./tests/bugs/nfs/bug-915280.t  -  5 second
./tests/bugs/nfs/bug-1143880-fix-gNFSd-auth-crash.t  -  5 second
./tests/bugs/md-cache/setxattr-prepoststat.t  -  5 second
./tests/bugs/io-stats/bug-1598548.t  -  5 second
./tests/bugs/io-cache/bug-read-hang.t  -  5 second
./tests/bugs/glusterfs/bug-861015-log.t  -  5 second
./tests/bugs/glusterfs/bug-848251.t  -  5 second
./tests/bugs/fuse/bug-1030208.t  -  5 second
./tests/bugs/ec/bug-1227869.t  -  5 second
./tests/bugs/distribute/bug-884597.t  -  5 second
./tests/bugs/core/bug-908146.t  -  5 second
./tests/bugs/core/bug-1168803-snapd-option-validation-fix.t  -  5 second
./tests/bugs/cli/bug-1022905.t  -  5 second
./tests/bugs/bug-1371806_2.t  -  5 second
./tests/bugs/bug-1258069.t  -  5 second
./tests/bugs/bitrot/1209751-bitrot-scrub-tunable-reset.t  -  5 second
./tests/bugs/bitrot/1207029-bitrot-daemon-should-start-on-valid-node.t  -  5 
second
./tests/basic/volume-status.t  -  5 second
./tests/basic/posix/zero-fill-enospace.t  -  5 second
./tests/basic/glusterd/arbiter-volume.t  -  5 second
./tests/basic/gfapi/upcall-cache-invalidate.t  -  5 second
./tests/basic/gfapi/gfapi-dup.t  -  5 second
./tests/basic/gfapi/bug-1241104.t  -  5 second
./tests/basic/gfapi/anonymous_fd.t  -  5 second
./tests/basic/ec/ec-read-policy.t  -  5 second
./tests/basic/ec/ec-fallocate.t  -  5 second
./tests/basic/ctime/ctime-noatime.t  -  5 second
./tests/basic/ctime/ctime-glfs-init.t  -  5 second
./tests/basic/afr/ta.t  -  5 second
./tests/basic/afr/tarissue.t  -  5 second
./tests/basic/afr/gfid-heal.t  -  5 second
./tests/performance/quick-read.t  -  4 second
./tests/bugs/upcall/bug-upcall-stat.t  -  4 second
./tests/bugs/transport/bug-873367.t  -  4 second
./tests/bugs/shard/bug-1272986.t  -  4 second
./tests/bugs/shard/bug-1259651.t  -  4 second
./tests/bugs/shard/bug-1258334.t  -  4 second
./tests/bugs/replicate/bug-1250170-fsync.t  -  4 second
./tests/bugs/quota/bug-1287996.t  -  4 second
./tests/bugs/quota/bug-1104692.t  -  4 second
./tests/bugs/posix/disallow-gfid-volumeid-fremovexattr.t  -  4 second
./tests/bugs/posix/bug-1034716.t  -  4 second
./tests/bugs/nfs/zero-atime.t  -  4 second
./tests/bugs/nfs/subdir-trailing-slash.t  -  4 second
./tests/bugs/nfs/socket-as-fifo.t  -  4 second
./tests/bugs/nfs/bug-877885.t  -  4 second
./tests/bugs/nfs/bug-847622.t  -  4 second
./tests/bugs/nfs/bug-1210338.t  -  4 second

[Gluster-Maintainers] glusterfs-5.4 released

2019-02-26 Thread jenkins 
SRC: https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
HASH: 
https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum

This release is made off jenkins-release-80___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] Release 5.4: Earlier than Mar-10th

2019-02-26 Thread Shyam Ranganathan 
Thank you all, merging the patches and tagging the release today.

Shyam
On 2/26/19 6:50 AM, Atin Mukherjee wrote:
> Milind - response inline.
> 
> Shyam - I'm not sure if you're tracking this. But at this point any
> blocker bugs attached to 5.4 should also have clones of release-6 and
> attached to the release tracker, otherwise we'll regress!
> 
> On Tue, Feb 26, 2019 at 5:00 PM Milind Changire  > wrote:
> 
> On Fri, Feb 8, 2019 at 8:26 PM Shyam Ranganathan
> mailto:srang...@redhat.com>> wrote:
> 
> Hi,
> 
> There have been several crashes and issues reported by users on the
> latest 5.3 release. Around 10 patches have been merged since 5.3
> and we
> have a few more addressing the blockers against 5.4 [1].
> 
> The original date was March 10th, but we would like to
> accelerate a 5.4
> release to earlier this month, once all critical blockers are fixed.
> 
> Hence there are 3 asks in this mail,
> 
> 1) Packaging team, would it be possible to accommodate an 5.4
> release
> around mid-next week (RC0 for rel-6 is also on the same week)?
> Assuming
> we get the required fixes by then.
> 
> 2) Maintainers, what other issues need to be tracked as
> blockers? Please
> add them to [1].
> 
> 3) Current blocker status reads as follows:
> - Bug 1651246 - Failed to dispatch handler
>   - This shows 2 patches that are merged, but there is no patch that
> claims this is "Fixed" hence bug is still in POST state. What other
> fixes are we expecting on this?
>   - @Milind request you to update the status
> 
> Bug 1651246 has been addressed.
> Patch has been merged on master
>  as well as
> release-5  branches.
> Above patch addresses logging issue only.
> 
> 
> Isn't this something which is applicable to release-6 branch as well? I
> don't find https://review.gluster.org/#/c/glusterfs/+/1/ in
> release-6 branch which means we're going to regress this in release 6 if
> this isn't backported and marked as blocker to release 6.
> 
> 
> 
> - Bug 1671556 - glusterfs FUSE client crashing every few days with
> 'Failed to dispatch handler'
>   - Awaiting fixes for identified issues
>   - @Nithya what would be the target date?
> 
> - Bug 1671603 - flooding of "dict is NULL" logging & crash of
> client process
>   - Awaiting a fix, what is the potential target date for the same?
>   - We also need the bug assigned to a person
> 
> Bug 1671603 has been addressed.
> Patch has been posted on master
>  and merged on
> release-5  branches.
> 
> 
> Are you sure the links are correct? Patch posted against release 5
> branch is abandoned? And also just like above, same question for
> release-6 branch, I don't see a patch?
> 
> Above patch addresses logging issue only.
> 
> 
> Thanks,
> Shyam
> 
> [1] Release 5.4 tracker:
> https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4
> ___
> maintainers mailing list
> maintainers@gluster.org 
> https://lists.gluster.org/mailman/listinfo/maintainers
> 
> 
> 
> -- 
> Milind
> 
> ___
> maintainers mailing list
> maintainers@gluster.org 
> https://lists.gluster.org/mailman/listinfo/maintainers
> 
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] Release 5.4: Earlier than Mar-10th

2019-02-26 Thread Atin Mukherjee 
Milind - response inline.

Shyam - I'm not sure if you're tracking this. But at this point any blocker
bugs attached to 5.4 should also have clones of release-6 and attached to
the release tracker, otherwise we'll regress!

On Tue, Feb 26, 2019 at 5:00 PM Milind Changire  wrote:

> On Fri, Feb 8, 2019 at 8:26 PM Shyam Ranganathan 
> wrote:
>
>> Hi,
>>
>> There have been several crashes and issues reported by users on the
>> latest 5.3 release. Around 10 patches have been merged since 5.3 and we
>> have a few more addressing the blockers against 5.4 [1].
>>
>> The original date was March 10th, but we would like to accelerate a 5.4
>> release to earlier this month, once all critical blockers are fixed.
>>
>> Hence there are 3 asks in this mail,
>>
>> 1) Packaging team, would it be possible to accommodate an 5.4 release
>> around mid-next week (RC0 for rel-6 is also on the same week)? Assuming
>> we get the required fixes by then.
>>
>> 2) Maintainers, what other issues need to be tracked as blockers? Please
>> add them to [1].
>>
>> 3) Current blocker status reads as follows:
>> - Bug 1651246 - Failed to dispatch handler
>>   - This shows 2 patches that are merged, but there is no patch that
>> claims this is "Fixed" hence bug is still in POST state. What other
>> fixes are we expecting on this?
>>   - @Milind request you to update the status
>>
> Bug 1651246 has been addressed.
> Patch has been merged on master
>  as well as release-5
>  branches.
> Above patch addresses logging issue only.
>

Isn't this something which is applicable to release-6 branch as well? I
don't find https://review.gluster.org/#/c/glusterfs/+/1/ in release-6
branch which means we're going to regress this in release 6 if this isn't
backported and marked as blocker to release 6.


>
>> - Bug 1671556 - glusterfs FUSE client crashing every few days with
>> 'Failed to dispatch handler'
>>   - Awaiting fixes for identified issues
>>   - @Nithya what would be the target date?
>>
>> - Bug 1671603 - flooding of "dict is NULL" logging & crash of client
>> process
>>   - Awaiting a fix, what is the potential target date for the same?
>>   - We also need the bug assigned to a person
>>
> Bug 1671603 has been addressed.
> Patch has been posted on master
>  and merged on release-5
>  branches.
>

Are you sure the links are correct? Patch posted against release 5 branch
is abandoned? And also just like above, same question for release-6 branch,
I don't see a patch?

Above patch addresses logging issue only.
>
>
>> Thanks,
>> Shyam
>>
>> [1] Release 5.4 tracker:
>> https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4
>> ___
>> maintainers mailing list
>> maintainers@gluster.org
>> https://lists.gluster.org/mailman/listinfo/maintainers
>>
>
>
> --
> Milind
>
> ___
> maintainers mailing list
> maintainers@gluster.org
> https://lists.gluster.org/mailman/listinfo/maintainers
>
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] Release 5.4: Earlier than Mar-10th

2019-02-26 Thread Milind Changire 
On Fri, Feb 8, 2019 at 8:26 PM Shyam Ranganathan 
wrote:

> Hi,
>
> There have been several crashes and issues reported by users on the
> latest 5.3 release. Around 10 patches have been merged since 5.3 and we
> have a few more addressing the blockers against 5.4 [1].
>
> The original date was March 10th, but we would like to accelerate a 5.4
> release to earlier this month, once all critical blockers are fixed.
>
> Hence there are 3 asks in this mail,
>
> 1) Packaging team, would it be possible to accommodate an 5.4 release
> around mid-next week (RC0 for rel-6 is also on the same week)? Assuming
> we get the required fixes by then.
>
> 2) Maintainers, what other issues need to be tracked as blockers? Please
> add them to [1].
>
> 3) Current blocker status reads as follows:
> - Bug 1651246 - Failed to dispatch handler
>   - This shows 2 patches that are merged, but there is no patch that
> claims this is "Fixed" hence bug is still in POST state. What other
> fixes are we expecting on this?
>   - @Milind request you to update the status
>
Bug 1651246 has been addressed.
Patch has been merged on master
 as well as release-5
 branches.
Above patch addresses logging issue only.


> - Bug 1671556 - glusterfs FUSE client crashing every few days with
> 'Failed to dispatch handler'
>   - Awaiting fixes for identified issues
>   - @Nithya what would be the target date?
>
> - Bug 1671603 - flooding of "dict is NULL" logging & crash of client
> process
>   - Awaiting a fix, what is the potential target date for the same?
>   - We also need the bug assigned to a person
>
Bug 1671603 has been addressed.
Patch has been posted on master
 and merged on release-5
 branches.
Above patch addresses logging issue only.


> Thanks,
> Shyam
>
> [1] Release 5.4 tracker:
> https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4
> ___
> maintainers mailing list
> maintainers@gluster.org
> https://lists.gluster.org/mailman/listinfo/maintainers
>


-- 
Milind
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] Release 5.4: Earlier than Mar-10th

2019-02-26 Thread Aravinda 
On Mon, 2019-02-25 at 10:42 -0500, Shyam Ranganathan wrote:
> Time to reset and understand where we are at here. The dates are
> slipping, but the tracker is still having the following blockers.
> 
> We need to either understand when these would be fixed, and take a
> call
> on creating 5.4 with known issues not addressed in the blocker, or
> wait
> for the fixes. Responses to the bugs and updates to bugzilla would
> help
> deciding on the same.
> 
> 1) Title: glustereventsd does not start on Ubuntu 16.04 LTS
> https://bugzilla.redhat.com/show_bug.cgi?id=1649054
> 
> @aravinda, any updates? Should we wait, of will this take more time?

Patch merged in master and release-5 Patch yet to be merged
https://review.gluster.org/#/c/glusterfs/+/22262/

> 
> 2) Title: glusterfs FUSE client crashing every few days with 'Failed
> to
> dispatch handler'
> https://bugzilla.redhat.com/show_bug.cgi?id=1671556
> 
> All patches against the bug are merged, but bug remains in POST
> state,
> as none of the patches claim that the issue "Fixes" the reported
> problem.
> 
> Are we awaiting more patches for the same? Du/Milind/Nithya?
> 
> 3) Title: flooding of "dict is NULL" logging & crash of client
> process
> https://bugzilla.redhat.com/show_bug.cgi?id=1671603
> 
> Still in NEW state, Du/Amar, do we have a date for resolution?
> 
> Thanks,
> Shyam
> On 2/18/19 10:13 AM, Shyam Ranganathan wrote:
> > We have more blockers against 5.4 now marked. Would like to ask the
> > list
> > and understand what we want to get done with by 5.4 and what the
> > timeline looks like.
> > 
> > The bug list:
> > https://bugzilla.redhat.com/buglist.cgi?bug_id=1667103_id_type=anddependson=tvp
> > 
> > 1) https://bugzilla.redhat.com/show_bug.cgi?id=1649054
> > Title: glustereventsd does not start on Ubuntu 16.04 LTS
> > Assignee: Aravinda
> > @aravinda can we understand target dates here?
> > 
> > 2) https://bugzilla.redhat.com/show_bug.cgi?id=1671556
> > Title: glusterfs FUSE client crashing every few days with 'Failed
> > to
> > dispatch handler'
> > Assignee: Nithya (working on Du and Milind)
> > @du/@milind can we get an update on this bug and how far away we
> > are?
> > 
> > 3) https://bugzilla.redhat.com/show_bug.cgi?id=1671603
> > Title: flooding of "dict is NULL" logging & crash of client process
> > Assignee: None (Amar has most of the comments)
> > @amar, do we need 2 bugs here? Also, how far away is a fix?
> > 
> > 4) https://bugzilla.redhat.com/show_bug.cgi?id=1676356
> > Title: glusterfs FUSE client crashing every few days with 'Failed
> > to
> > dispatch handler'
> > Assignee: Du
> > @du, we are still waiting to get
> > https://review.gluster.org/c/glusterfs/+/22189 merged, right?
> > 
> > Shyam
> > On 2/13/19 4:09 AM, Raghavendra Gowdappa wrote:
> > > 
> > > On Wed, Feb 13, 2019 at 2:24 PM Nithya Balachandran <
> > > nbala...@redhat.com
> > > > wrote:
> > > 
> > > Adding Raghavendra G and Milind who are working on the
> > > patches so
> > > they can update on when they should be ready.
> > > 
> > > On Fri, 8 Feb 2019 at 20:26, Shyam Ranganathan <
> > > srang...@redhat.com
> > > > wrote:
> > > 
> > > Hi,
> > > 
> > > There have been several crashes and issues reported by
> > > users on the
> > > latest 5.3 release. Around 10 patches have been merged
> > > since 5.3
> > > and we
> > > have a few more addressing the blockers against 5.4 [1].
> > > 
> > > The original date was March 10th, but we would like to
> > > accelerate a 5.4
> > > release to earlier this month, once all critical blockers
> > > are fixed.
> > > 
> > > Hence there are 3 asks in this mail,
> > > 
> > > 1) Packaging team, would it be possible to accommodate an
> > > 5.4
> > > release
> > > around mid-next week (RC0 for rel-6 is also on the same
> > > week)?
> > > Assuming
> > > we get the required fixes by then.
> > > 
> > > 2) Maintainers, what other issues need to be tracked as
> > > blockers? Please
> > > add them to [1].
> > > 
> > > 3) Current blocker status reads as follows:
> > > - Bug 1651246 - Failed to dispatch handler
> > >   - This shows 2 patches that are merged, but there is no
> > > patch that
> > > claims this is "Fixed" hence bug is still in POST state.
> > > What other
> > > fixes are we expecting on this?
> > >   - @Milind request you to update the status
> > > 
> > > - Bug 1671556 - glusterfs FUSE client crashing every few
> > > days with
> > > 'Failed to dispatch handler'
> > >   - Awaiting fixes for identified issues
> > >   - @Nithya what would be the target date?
> > > 
> > > 
> > > Fix @ https://review.gluster.org/#/c/glusterfs/+/22189/
> > > 
> > > waiting on reviews. I am hoping to get this merged by end of this
> > > week
> > > and send a backport.
> > >