ERROR: duplicate key value violates unique constraint "ix_4f0315b8"_ Detail: Key (buildnamespace, buildnumber)=(FOO, 29) already exists.

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.2.X
• Fix Version/s: 7.2.10 DXP FP13, 7.2.X, 7.3.7 CE GA8, 7.3.10 DXP FP2, 7.3.X, 7.4.0 CE GA1, 7.4.1 CE GA2, 7.4.13 DXP GA1, Master
• Component/s: Core Infrastructure > Service Builder
• Labels:
  • ee-ts
  • liferay-fixpack-dxp-13-7210
  • liferay-fixpack-dxp-2-7310
• Branch Version/s:
  7.3.x, 7.2.x
• Backported to Branch:
  Committed
• Fix Priority: 3
• Git Pull Request: https://github.com/shuyangzhou/liferay-portal/pull/9926

Description: When using a cluster of at least two nodes the second node throws an error "ERROR: duplicate key value violates unique constraint "ix_4f0315b8"_ Detail: Key (buildnamespace, buildnumber)=(FOO, 29) already exists." when trying to deploy a service builder with a new buildNumber because already exists in the database in ServiceComponent table updated by deploying on the first node.

Steps to reproduce:
1. Create a cluster of two nodes node1 and node2 using cluster.link.enabled=true in portal-ext.properties pointing to same database https://help.liferay.com/hc/en-us/articles/360018175191-Liferay-DXP-Clustering
2. Create a service builder module or use the one attached for DXP 7.2 
3. Deploy for the first time in both nodes, first node1 and then node2, it should work properly for the first time
4. Now increase the buildNumber by running Gradle buildService task and follow to next step
5. Deploy first in node1 wait until is done, then deploy in node2, now the error should be thrown on this second node 

Actual: Errors occurs when deploying service build module with a new buildNumber in a cluster with more than a node.

Expected: No errors occurs when deploying service build module with a new buildNumber in a cluster with more than a node.

_{* Please see Zendesk Support tab for further comments and attachments.}