That error is indicating that you’re trying to instantiate a vf-module that SDNC doesn’t recognize. SDNC gets a feed from SDC of TOSCA models. So, what seems to be happening here is that for some reason, the vf-module you’re trying to instantiate doesn’t match any of the TOSCA model data that SDNC has received. That ‘customization UUID’ is the key we use to match the incoming data in your request. Under the ‘vf-module-information / onap-model-information’, there’s a field called ‘model-customization-uuid’, which has to match the customization-uuid defined for that vf-module in the TOSCA model.
That’s what SDNC specifically is complaining about. To fix it, if you happen to know the TOSCA model that defines that vf-module, you can try to redistribute the model from SDC to see if that helps. If not, it’s possible that for some reason SDNC is not able to ingest that model (due to some data error maybe?). If that’s the case, there should be an error in the sdnc-ueb-listener pod that you should be able to see via kubectl logs.
Hope this helps – good luck!
onap-discuss <onap-discuss@...> on behalf of Ali Akbar Hemmati <hemmati.ali.a@...>
Hi ONAP community,