-
Bug
-
Resolution: Done
-
Medium
-
None
-
None
-
None
After create a connectivity service, the NEPs of the T-API node used in the connectivity service are populated with the corresponding CEPs. The function that was getting the T-API nodes from the topology was not including in the response the NEPs that had CEP information created and therefore some NEPs where missing. This was causing an error when performing a create-connectivity-service-request as the SIP in the request was not found in any node of the T-API topology
- duplicates
-
TRNSPRTPCE-552 create connectivity service returns "Nep not found in datastore" when creating a second time a connectivity service
- Verified
- is duplicated by
-
TRNSPRTPCE-552 create connectivity service returns "Nep not found in datastore" when creating a second time a connectivity service
- Verified