similar to: Kubernetes v1.7.3 and GlusterFS Plugin

short copy from a kubectl describe pod... Events: FirstSeen LastSeen Count From SubObjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 5h 54s 173 kubelet, k8s-bootcamp-rbac-np-worker-6263f70 Warning FailedMount (combined from similar events): MountVolume.SetUp failed for volume "pvc-fa4b2621-7dad-11e7-8a44-062df200059f" : glusterfs:

Just created the container from here: https://github.com/gluster/gluster-containers/tree/master/CentOS And used stock Kubernetes 1.7.3, hence the included volume plugin and Heketi version 4. Humble Devassy Chirammal <humble.devassy at gmail.com> schrieb am Do., 10. Aug. 2017, 18:49: > ?Thanks .. Its the same option. Can you let me know your glusterfs client > package version ?? >

Ok, thanks. Humble Devassy Chirammal <humble.devassy at gmail.com> schrieb am Do., 10. Aug. 2017, 19:04: > On Thu, Aug 10, 2017 at 10:25 PM, Christopher Schmidt <fakod666 at gmail.com> > wrote: > >> Just created the container from here: >> https://github.com/gluster/gluster-containers/tree/master/CentOS >> >> And used stock Kubernetes 1.7.3, hence the

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

?Thanks .. Its the same option. Can you let me know your glusterfs client package version ?? On Thu, Aug 10, 2017 at 8:34 PM, Christopher Schmidt <fakod666 at gmail.com> wrote: > > short copy from a kubectl describe pod... > > Events: > FirstSeen LastSeen Count From SubObjectPath Type Reason Message > --------- -------- ----- ---- ------------- -------- ------

On Thu, Aug 10, 2017 at 10:25 PM, Christopher Schmidt <fakod666 at gmail.com> wrote: > Just created the container from here: https://github.com/gluster/ > gluster-containers/tree/master/CentOS > > And used stock Kubernetes 1.7.3, hence the included volume plugin and > Heketi version 4. > > ? Regardless of the glusterfs client version this is supposed to work. One patch

As an another solution, if you are updating the system where you run application container to latest glusterfs ( 3.11) , this will be fixed as well as it support this mount option. --Humble On Thu, Aug 10, 2017 at 10:39 PM, Christopher Schmidt <fakod666 at gmail.com> wrote: > Ok, thanks. > > Humble Devassy Chirammal <humble.devassy at gmail.com> schrieb am Do., 10. >

Yes, I tried to, but I didn't find a 3.11 centos-release-gluster package for CentOS. Humble Devassy Chirammal <humble.devassy at gmail.com> schrieb am Do., 10. Aug. 2017, 19:17: > As an another solution, if you are updating the system where you run > application container to latest glusterfs ( 3.11) , this will be fixed as > well as it support this mount option. > >

On 8 November 2017 at 02:47, Sam McLeod <mailinglists at smcleod.net> wrote: > > On 6 Nov 2017, at 3:32 pm, Laura Bailey <lbailey at redhat.com> wrote: > > Do the users have permission to see/interact with the directories, in > addition to the files? > > > Yes, full access to directories and files. > Also testing using the root user. > > > On Mon,

> On 8 Nov 2017, at 9:03 pm, Nithya Balachandran <nbalacha at redhat.com> wrote: > > > That is not the log for the mount. Please check /var/log/glusterfs/var-lib-mountedgluster.log on the system on which you are running the mount process. > > Please provide the volume config details as well (gluster volume info) from one of the server nodes. > Oh I'm sorry, I

Hi Talur, I've successfully got Gluster deployed as a DaemonSet using k8s spec file glusterfs-daemonset.json from https://github.com/heketi/heketi/tree/master/extras/kubernetes but then when I try deploying heketi using heketi-deployment.json spec file, I end up with a CrashLoopBackOff pod. # kubectl get pods NAME READY STATUS RESTARTS AGE

Adding more people to the thread. I am currently not able to analyze the logs. On Thu, Jul 27, 2017 at 5:58 AM, Bishoy Mikhael <b.s.mikhael at gmail.com> wrote: > Hi Talur, > > I've successfully got Gluster deployed as a DaemonSet using k8s spec file > glusterfs-daemonset.json from > https://github.com/heketi/heketi/tree/master/extras/kubernetes > > but then when I

Hi Bishoy, Adding Talur who can help address your queries on Heketi. @wattsteve's github repo on glusterfs-kubernetes is a bit dated. You can either refer to gluster/gluster-kubernetes or heketi/heketi for current documentation and operational procedures. Regards, Vijay On Fri, Jul 21, 2017 at 2:19 AM, Bishoy Mikhael <b.s.mikhael at gmail.com> wrote: > Hi, > > I'm

Hi, I'm trying to deploy Gluster and Heketi on a Kubernetes cluster I'm following the guide at https://github.com/gluster/gluster-kubernetes/ but the video referenced in the page is showing json files used while the git repo has only yaml files, they are quiet similar though, but Gluster is a deployment not a DaemonSet. I deploy Gluster DaemonSet successfully, but heketi is giving me the

Hello, I am trying to setup GitLab, Redis and PostgreSQL containers in Kubernetes using Gluster for persistence. GlusterFS nodes are setup on machines (CentOS) external to Kubernetes cluster (running on RancherOS host). Issue is that when GitLab tries starting up, the login page doesn't load. It's a fresh setup and not something that stopped working now. root at

Getting this answer back on the list in case anyone else is trying to share storage. Thanks for the docs pointer, Tanner. -John On Thu, Sep 7, 2017 at 6:50 PM, Tanner Bruce <tanner.bruce at farmersedge.ca> wrote: > You can set a security context on your pod to set the guid as needed: > https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ > > > This

https://bugzilla.netfilter.org/show_bug.cgi?id=1396 Bug ID: 1396 Summary: When rule with 3 concat elements are added, nft list shows only 2 Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: critical Priority: P5 Component: nft

I just realised that I haven't touched a centos/redhat machine in more than a couple of years. Everything I do now is Kubernetes based or using cloud services (or k8s cloud services). What about it listeroons? Is your fleet of centos boxes ever expanding or are you just taking care of a single java 6 jboss application that takes care of the companies widget stocks? How are your jobs

All, I am trying to configure hdlc support on T100P Digium card - everything seems ok... but it just does not work at all. I was able to compile all drivers, the light on the card becomes green when I plug T1 link.... but I even can't ping default router IP... there is no data coming back to me, so I am confused completely now. Also I tried both protocols - raw hdlc and cisco hdlc. The

> What OS are your k8s clusters running on? How about your cloud > providers? Mine are on RHEL and CentOS. > I don't know. We use fully managed services from Google. I think its coreOS. > -- > Jonathan Billings <billings at negate.org> > _______________________________________________ > CentOS mailing list > CentOS at centos.org >