p_kubernetes_rancher.html#onap-on-kubernetes-with-rancher
br,
Michal
- Original Message -----
Sender : Michael Still mailto:mi...@stillhq.com>>
Date : 2018-06-19 04:57 (GMT+1)
Title : Re: [onap-discuss] AAF kubernetes pods failing
To : wkurki...@gmail.com<mailto:wkurki
t;
>
>
> - *Original Message* -
>
> *Sender* : Michael Still
>
> *Date* : 2018-06-19 04:57 (GMT+1)
>
> *Title* : Re: [onap-discuss] AAF kubernetes pods failing
>
> *To : *wkurki...@gmail.com
>
> *CC : *onap-discuss@lists.onap.org
>
>
>
m.git/docs/oom_setup_kubernetes_rancher.html#onap-on-kubernetes-with-rancher
br,
Michal
- Original Message -
Sender : Michael Still
Date : 2018-06-19 04:57 (GMT+1)
Title : Re: [onap-discuss] AAF kubernetes pods failing
To : wkurki...@gmail.com
CC : onap-discuss@list
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
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
