Situation: A service has two resources R1 and R2.

1. Distribute the service v1.0 from SDC to SO. Everything is good.
2. In SDC, modify R1 but keep R2 the same. Now distribute the service v2.0 to SO would fail.

The failure happens when insert R2 to table SERVICE_TO_RESOURCE_CUSTOMIZATIONS. The problem is that R2 already exists in the table and is linked to the service v1.0

Now SO tries to add R2 again to the table and this time it is linked to service v2.0. An error is reported.

Note that from v1.0 to v2.0, the uuid of the service has changed, but the uuid and customization id of R2 does not change since that resource is not modified at all.

If it is OK for SO to allow one resource customization uuid be linked to multiple services, please fix this in SO.

If SO thinks it is necessary that each time a service is updated to a new version, all the resources it contains should be assigned new customization UUIDs, then please reassign this task to SDC.

Below is what I extracted from SO docker ASDCController/errormso.log:

29 more - Caused by: org.mariadb.jdbc.internal.util.dao.QueryException: Duplicate entry 'allottedResource-cda7b93c-f742-478e-9262-a457ed6c2844' for key 'PRIMARY' - Query is: insert into SERVICE_TO_RESOURCE_CUSTOMIZATIONS (SERVICE_MODEL_UUID, MODEL_TYPE, RESOURCE_MODEL_CUSTOMIZATION_UUID) values (?, ?, ?), parameters ['937a6a9c-c1aa-4a02-993a-0def57ce9063','allottedResource','cda7b93c-f742-478e-9262-a457ed6c2844'] -