Formerly VNFC in AAI information was being created by SDNC however the VNFC relation to the vserver was added till El Alto by robot heatbridge only. SDNC creates VNFC object and since Frankfurt SO heatbridge creates vservers. There is no entity responsible for the creation of relations between server and VNFC. As a result, VNFC object is the following:

https://10.12.5.248:30233/aai/v14/network/vnfcs/vnfc/vfwl02vfw8ccd?depth=all
returns

{
    "vnfc-name": "vfwl02vfw8ccd",
    "nfc-naming-code": "vFWDT",
    "nfc-function": "vFWDT",
    "ipaddress-v4-oam-vip": "10.0.110.4",
    "in-maint": false,
    "is-closed-loop-disabled": false,
    "resource-version": "1591952051391"
}

and there is no information about relations to vserver. vFWDT use case is instantiated with GR-API and with preload information. APPC requires information about VNFC to gather information about configuration template values' assignments in certain situations. in this particular case requires this information for IP information. This is a regression from RC0 tests and ElAlto and it prevents execution of the use case.