I upgrade policy helm chart to frankfurt latest version and
check that the naming policy is created and pushed OK.However, the SDNC error that occurred earlier was not resolved.
./demo-k8s.sh onap instantiateVLB_CDS
Instantiate VLB_CDS
demoVLB_CDS Service Already Exists
| FAIL |
Received failure response from so {"request":{"requestId":"e85ec7ad-26b1-4097-804d-8a1a58bd6cf8","startTime":"Tue, 02 Jun 2020 12:29:35 GMT","finishTime":"Tue, 02 Jun 2020 12:29:54 GMT","requestScope":"service","requestType":"createInstance","requestDetails":{"modelInfo":{"modelInvariantId":"0fa35a56-f349-4581-9ac7-b1b4e6bad162","modelType":"service","modelName":"demoVLB_CDS","modelVersion":"1.0","modelVersionId":"382eec08-bc04-4db3-89bd-2dc2f6624619","modelUuid":"382eec08-bc04-4db3-89bd-2dc2f6624619","modelInvariantUuid":"0fa35a56-f349-4581-9ac7-b1b4e6bad162"},"requestInfo":{"productFamilyId":"a9a77d5a-123e-4ca2-9eb9-0b015d2ee0fb","source":"VID","instanceName":"cds_vlb_svc_2020-06-02_212934","suppressRollback":false,"requestorId":"robot-ete"},"subscriberInfo":{"globalSubscriberId":"Demonstration"},"cloudConfiguration":{"tenantId":"1e9c8586aec441c389654f37d5112e01","tenantName":"admin","cloudOwner":"CloudOwner","lcpCloudRegionId":"RegionOne"},"requestParameters":{"subscriptionServiceType":"vLB","userParams":[{"Homing_Solution":"none"},{"service":{"instanceParams":[],"instanceName":"cds_vlb_svc_2020-06-02_212934","resources":{"vnfs":[{"modelInfo":{"modelName":"vLB_CDS 0fa6afe8-a28f","modelVersionId":"fe6f46f0-c667-41af-9a0d-dd31329b1c31","modelInvariantUuid":"13718ec5-bb5c-4558-9375-0be6a9a6edf1","modelVersion":"1.0","modelCustomizationId":"395d0af1-dfea-4675-985c-ee995fa68dd8","modelInstanceName":"vLB_CDS 0fa6afe8-a28f 0"},"cloudConfiguration":{"lcpCloudRegionId":"RegionOne","tenantId":"1e9c8586aec441c389654f37d5112e01"},"platform"...
[ Message content over the limit has been removed. ]
...7-4780-a7ae-15acdabf4d95","modelVersion":"1","modelCustomizationId":"37c6d462-25ec-45dc-a6a5-ed1676451e0c"},"instanceName":"VlbCds0fa6afe8A28f..vlb..module-2","instanceParams":[{}]},{"modelInfo":{"modelName":"VlbCds0fa6afe8A28f..vdns..module-3","modelVersionId":"bb6f2449-5e07-4132-b405-92add0ca3706","modelInvariantUuid":"15c0dead-610c-4b85-b156-995b0b140099","modelVersion":"1","modelCustomizationId":"2c10f633-de5b-4e11-a877-9f12e30aa0d8"},"instanceName":"VlbCds0fa6afe8A28f..vdns..module-3","instanceParams":[{}]}]}]},"modelInfo":{"modelVersion":"1.0","modelVersionId":"382eec08-bc04-4db3-89bd-2dc2f6624619","modelInvariantId":"0fa35a56-f349-4581-9ac7-b1b4e6bad162","modelName":"demoVLB_CDS","modelType":"service"}}}],"aLaCarte":false},"project":{"projectName":"Project-Demonstration"},"owningEntity":{"owningEntityId":"67f2e84c-734d-4e90-a1e4-d2ffa2e75849","owningEntityName":"OE-Demonstration"}},"instanceReferences":{"serviceInstanceId":"3ddbff6f-3460-41b3-beb3-bff45e6f2d4c","serviceInstanceName":"cds_vlb_svc_2020-06-02_212934","vnfInstanceId":"f223dcdb-28e2-45dc-9393-36fc94a7f573"},"requestStatus":{"requestState":"FAILED","statusMessage":"STATUS: Error Source: SDNC, Error Message: Failed to create self-serve assignment for vnf with vnf-id=f223dcdb-28e2-45dc-9393-36fc94a7f573 with error: Failed to get RA assignments: Error from BlueprintProcessingClient FLOW STATUS: All Rollback flows have completed successfully ROLLBACK STATUS: Rollback has been completed successfully.","percentProgress":100,"timestamp":"Tue, 02 Jun 2020 12:29:54 GMT"}}}
I am not sure what is the problem and what to do to solve this problem.
In mariaDB:
MariaDB [catalogdb]> select * from orchestration_flow_reference where COMPOSITE_ACTION='VFModule-Delete' order by id;
+-----+------------------+--------+----------------------+--------------+----------------------+-------+--------+
| id | COMPOSITE_ACTION | SEQ_NO | FLOW_NAME | FLOW_VERSION | NB_REQ_REF_LOOKUP_ID | SCOPE | ACTION |
+-----+------------------+--------+----------------------+--------------+----------------------+-------+--------+
| 660 | VFModule-Delete | 3 | DeactivateVfModuleBB | 1 | 135 | NULL | NULL |
| 663 | VFModule-Delete | 4 | DeleteVfModuleBB | 1 | 135 | NULL | NULL |
| 666 | VFModule-Delete | 5 | UnassignVfModuleBB | 1 | 135 | NULL | NULL |
+-----+------------------+--------+----------------------+--------------+----------------------+-------+--------+
The result is different from the Frankfurt vLB demo page. I think it affect the problem.
from orchestration_flow_reference table in catalogdb database, there are 167 rows in set. (command with : select * from orchestration_flow_reference;)
In the current mariadb-galera helm chart, the mariadbRootPassword for the config in value.yaml is commented out. Therefore, I was unable to log in to mariadb-galera as root user. So I removed the Helm mariadb-galera chart and reinstall it by setting the mariadbRootPassword in config and then re-install SO with new config of new mariadbRootPassword. This seems to be a problem with db.
Is it necessary to reinstall components under mariadb-galera in override.yaml?(It means components installed after mariadb Because the order is later. e.g. policy, portal, robot ... so, vid)
I tried to redistribute the K8S jobs related to mariadb config, but it seemed to have no effect.(Using kubectl replace command)
I'm waiting for someone's feedback.
Regards,
Won.
