search for: 0x4073bd

...terfs log to help diagnose this issue: [2017-08-10 15:02:12.260168] W [glusterfsd.c:1095:cleanup_and_exit] (-->/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f3e2477c62d] (-->/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064) [0x7f3e24e43064] (-->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xdd) [0x4073bd]))) 0-: received signum (15), shutting down [2017-08-10 15:02:12.260189] I [fuse-bridge.c:5475:fini] 0-fuse: Unmounting '/var/lib/kubelet/pods/fa4c6540-7dad-11e7-8a44-062df200059f/volumes/ kubernetes.io~glusterfs/pvc-fa4b2621-7dad-11e7-8a44-062df200059f'. 5h 32s 151 kubelet, k8s-bootcamp...

...e: >> [2017-08-10 15:02:12.260168] W [glusterfsd.c:1095:cleanup_and_exit] >> (-->/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f3e2477c62d] >> (-->/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064) [0x7f3e24e43064] >> (-->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xdd) [0x4073bd]))) 0-: >> received signum (15), shutting down >> [2017-08-10 15:02:12.260189] I [fuse-bridge.c:5475:fini] 0-fuse: >> Unmounting >> '/var/lib/kubelet/pods/fa4c6540-7dad-11e7-8a44-062df200059f/volumes/ >> kubernetes.io~glusterfs/pvc-fa4b2621-7dad-11e7-8a44-062df2000...

...15:02:12.260168] W [glusterfsd.c:1095:cleanup_and_exit] >>>> (-->/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f3e2477c62d] >>>> (-->/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064) [0x7f3e24e43064] >>>> (-->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xdd) [0x4073bd]))) 0-: >>>> received signum (15), shutting down >>>> [2017-08-10 15:02:12.260189] I [fuse-bridge.c:5475:fini] 0-fuse: >>>> Unmounting >>>> '/var/lib/kubelet/pods/fa4c6540-7dad-11e7-8a44-062df200059f/volumes/ >>>> kubernetes.io~gluster...

...agnose this issue: > [2017-08-10 15:02:12.260168] W [glusterfsd.c:1095:cleanup_and_exit] > (-->/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f3e2477c62d] > (-->/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064) [0x7f3e24e43064] > (-->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xdd) [0x4073bd]))) 0-: > received signum (15), shutting down > [2017-08-10 15:02:12.260189] I [fuse-bridge.c:5475:fini] 0-fuse: > Unmounting '/var/lib/kubelet/pods/fa4c6540-7dad-11e7-8a44- > 062df200059f/volumes/kubernetes.io~glusterfs/pvc-fa4b2621- > 7dad-11e7-8a44-062df200059f'. > >...

...[2017-08-10 15:02:12.260168] W [glusterfsd.c:1095:cleanup_and_exit] >>> (-->/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f3e2477c62d] >>> (-->/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064) [0x7f3e24e43064] >>> (-->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xdd) [0x4073bd]))) 0-: >>> received signum (15), shutting down >>> [2017-08-10 15:02:12.260189] I [fuse-bridge.c:5475:fini] 0-fuse: >>> Unmounting '/var/lib/kubelet/pods/fa4c6540-7dad-11e7-8a44- >>> 062df200059f/volumes/kubernetes.io~glusterfs/pvc-fa4b2621- >>> 7da...

...168] W [glusterfsd.c:1095:cleanup_and_exit] >>>>> (-->/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f3e2477c62d] >>>>> (-->/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064) [0x7f3e24e43064] >>>>> (-->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xdd) [0x4073bd]))) 0-: >>>>> received signum (15), shutting down >>>>> [2017-08-10 15:02:12.260189] I [fuse-bridge.c:5475:fini] 0-fuse: >>>>> Unmounting '/var/lib/kubelet/pods/fa4c6540-7dad-11e7-8a44- >>>>> 062df200059f/volumes/kubernetes.io~glusterf...

...terfsd.c:1095:cleanup_and_exit] >>>>>> (-->/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f3e2477c62d] >>>>>> (-->/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064) [0x7f3e24e43064] >>>>>> (-->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xdd) [0x4073bd]))) 0-: >>>>>> received signum (15), shutting down >>>>>> [2017-08-10 15:02:12.260189] I [fuse-bridge.c:5475:fini] 0-fuse: >>>>>> Unmounting >>>>>> '/var/lib/kubelet/pods/fa4c6540-7dad-11e7-8a44-062df200059f/volumes/ >&g...

Are you seeing issue or error message which says auto_unmount option is not valid ? Can you please let me the issue you are seeing with 1.7.3 ? --Humble On Thu, Aug 10, 2017 at 3:33 PM, Christopher Schmidt <fakod666 at gmail.com> wrote: > Hi all, > > I am testing K8s 1.7.3 together with GlusterFS and have some issues > > is this correct? > - Kubernetes v1.7.3 ships

Hi all, I am testing K8s 1.7.3 together with GlusterFS and have some issues is this correct? - Kubernetes v1.7.3 ships with a GlusterFS Plugin that depends on GlusterFS 3.11 - GlusterFS 3.11 is not recommended for production. So 3.10 should be used This actually means no K8s 1.7.x version, right? Or is there anything else I could do? best Christopher -------------- next part -------------- An