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

Reply via email to