Hi, Could you look at the log of Policy for errors, for that you need to go in the pod themselves, under /var/log/onap. You could do the same for SDC container (backend). The thing that could have affect Policy is the fact we removed the persisted data of mariadb, because it was bogus (https://gerrit.onap.org/r/#/c/27521/ <https://gerrit.onap.org/r/#/c/27521/>). But I doubt it does explain your issue. Beside that, nothing having a potential disruptive effect happen to policy. The DCAE work was well tested before it got merged. I’ll re-test sometime today or early next week to make sure nothing has slept through the crack.
Thanks, Alexis > On Jan 18, 2018, at 11:44 PM, Ramanarayanan, Karthick <[email protected]> > wrote: > > Hi, > Trying to distribute a demo firewall service instance on a kubernetes host > running ONAP, I am seeing a new policy exception error on the latest oom on > amsterdam. > (dcae deploy is false and disableDcae is true) > > Error code: POL5000 > Status code: 500 > Internal Server Error. Please try again later. > > All pods are up. Health check seems to be fine on all pods. > k8s pod logs don't seem to reveal anything and this happens consistently > whenever I try to distribute the service as an operator. > > It was working fine last week. > Even yesterday I didn't get this error though I got a different one related > createVnfInfra notify exception on SO vnf create workflow step but that was a > different failure than this. > > After the dcae config changes got merged, this service distribution error > seems to have popped up. (dcae is disabled for my setup) > > What am I missing? > > Thanks, > -Karthick > _______________________________________________ > onap-discuss mailing list > [email protected] <mailto:[email protected]> > https://lists.onap.org/mailman/listinfo/onap-discuss > <https://lists.onap.org/mailman/listinfo/onap-discuss>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
