Thanks for this. You're totally right, I didn't have a shared NFS mount across the kubelets. Interestingly I can't see this mentioned in the getting started guide or the install guide. I concede its in the kube setup guide though.
Is there are good reason that OOM isn't using more traditional persistent volume claims via kubernetes storage providers? Thanks, Michael On Tue, Jun 19, 2018 at 5:24 PM Michal Ptacek <[email protected]> wrote: > Hi, > > > > I believe that this problem might be caused by missing mountpoint > /opt/app/osaaf > > this might pop-up when nfs share is not established across computes > > see "Setting up an NFS share for Multinode Kubernetes Clusters" in > > > http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_setup_kubernetes_rancher.html#onap-on-kubernetes-with-rancher > > > > br, > > Michal > > > > --------- *Original Message* --------- > > *Sender* : Michael Still <[email protected]> > > *Date* : 2018-06-19 04:57 (GMT+1) > > *Title* : Re: [onap-discuss] AAF kubernetes pods failing > > *To : *[email protected] > > *CC : *[email protected] > > > > Hi, I am seeing exactly this problem today with an attempted Beijing > install using OOM. The aaf-locate container is logging: > > > > /bin/bash: /opt/app/osaaf/logs/locate/stdout`date -I`: No such file or > directory > > > > Has anyone found a work-around for this? > > > > Thanks, > > Michael > > > > > > > > On Sat, May 12, 2018 at 6:48 AM William Kurkian <[email protected]> > wrote: > > Hello, > > > > On my onap install, most of the AAF pods are not starting. It seems to be > largely because of one pod that has an error sending it into > CrashLoopBackoff. It is the aaf-locate pod and it gets this error: > > > > /bin/bash: /opt/app/osaaf/logs/locate/stdout`date -I`: No such file or > directory > > > > Is this known and expected? or is it some issue on my machine? > > > > Thanks, > > William Kurkian > > _______________________________________________ > onap-discuss mailing list > [email protected] > https://lists.onap.org/mailman/listinfo/onap-discuss > > > -- > > Did this email leave you hoping to cause me pain? Good news! > > Sponsor me in city2surf 2018 and I promise to suffer greatly. > > http://www.madebymikal.com/city2surf-2018/ > > _______________________________________________ > > onap-discuss mailing list > > [email protected] > > https://lists.onap.org/mailman/listinfo/onap-discuss > > > > > > > -- Did this email leave you hoping to cause me pain? Good news! Sponsor me in city2surf 2018 and I promise to suffer greatly. http://www.madebymikal.com/city2surf-2018/
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
