While testing the overall regard-update-approval-status , noticed that OKM after receiving regard-application 2 times , parallelly its creating the regarded application LTP and fc-port instance twice resulting in having non unique uuids in the client/serve-ltps and fc-port.
(A similar scenario was handled in RO by @IswaryaaS , the same shall be applied here )
While testing the overall regard-update-approval-status , noticed that OKM after receiving regard-application 2 times , parallelly its creating the regarded application LTP and fc-port instance twice resulting in having non unique uuids in the client/serve-ltps and fc-port.
(A similar scenario was handled in RO by @IswaryaaS , the same shall be applied here )