[TRNSPRTPCE-552] create connectivity service returns "Nep not found in datastore" when creating a second time a connectivity service Created: 19/Oct/21 Updated: 10/Dec/21 Resolved: 19/Nov/21 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | Phosphorus |
| Fix Version/s: | None |
| Type: | Bug | Priority: | High |
| Reporter: | Christophe BETOULE | Assignee: | Javier Errea |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Epic Link: | T-API extended support | ||||||||||||
| Description |
|
When calling a connectivity service again (after a first creation and deletion of a connectivity service), the tapi connectivity service creation fails and returns the following log error : "Nep not found in datastore". |