-
Bug
-
Resolution: Done
-
High
-
Dublin Release
-
None
-
None
Solved issue! Find attached log traces and CBA used to perform the test.
Error Description
{
"errorMessage":
{ "message": "Generic failure. Details :
{failed to get source(processor-db) mapping}",
"code": 1,
"debugMessage": "ControllerBluePrint_Error_Message",
"timestamp": "2019-05-12T18:35:11.846Z"
}
}
Abdel and I have been going over the DDs for Dublin for vDNS and we found that in some case we are using primary-db and other processor-db.
Both source capabilities have reference in the code. Is the plan for Dublin to keep them both if yes, then we need to fix the disctionary_schema to include processor-db.
In addition, I believe the capability is missing in the schema as well.
Please see below reference:
| object ResourceDictionaryConstants { | |
| const val SOURCE_INPUT = "input" | |
| const val SOURCE_DEFAULT = "default" | |
| //const val SOURCE_PRIMARY_CONFIG_DATA = "rest" | |
| const val SOURCE_PROCESSOR_DB = "processor-db" | |
| const val SOURCE_PRIMARY_CONFIG_DATA = "primary-config-data" | |
| const val SOURCE_PRIMARY_DB = "primary-db" | |
| const val SOURCE_PRIMARY_AAI_DATA = "primary-aai-data" |
No reference to primary-db for below two links.
| resourceSourceMappings= input=source-input, default=source-default, processor-db=source-processor-db, primary-config-data=source-rest, capability=source-capability |
|
NOTE: missing aai reference
resourceSourceMappings=
input=source-input,
default=source-default,
processor-db=source-processor-db,
primary-config-data=source-rest,
primary-aai-data=source-rest,
capability=source-capability
resourceSourceMappings=
input=source-input,
default=source-default,
processor-db=source-processor-db,
primary-config-data=source-rest,
capability=source-capability
