[TRNSPRTPCE-115] Deleting node in clli-network Created: 06/May/19 Updated: 12/Jul/19 Resolved: 02/Jul/19 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | Jonas Mårtensson | Assignee: | Olivier Renais |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 2 hours | ||
| Original Estimate: | Not Specified | ||
| Description |
|
As discussed in |
| Comments |
| Comment by Jonas Mårtensson [ 11/Jun/19 ] |
|
How was this resolved? |
| Comment by Olivier Renais [ 13/Jun/19 ] |
|
Change back the status to unresolve since I am not sure we completely adress the comment. |
| Comment by Olivier Renais [ 13/Jun/19 ] |
|
Agree with your view regarding what implements deleteOpenROADM Node. The intent is to delete the CLLI node as the Network node disappear. Fortunately there is a bug which leads at the end to the expected behavior (we try to delete a CLLI that corresponds to the node Id and does not exist : as an example if we have ROADMA in CLLI NodeA, we try to delete the CLLI ROADMA which does not exist). Indeed, we do not expect a CLLI to be removed from the topo just because one of the nodes hosted in this CLLI has disappeared. CLLI correspond to buildings/rooms. They are not supposed to be removed from the topology just becaus an equuipment in that room fails. Will put the bug in the next sprint (focused on topology and portmapping consolidation) and we will remove the function to delete CLLI. |