Fix the order of deletion for 400G Ethernet service
ODUFlex, ODUC4
JIRA: TRNSPRTPCE-614
Signed-off-by: Balagangadhar Bathula <bb4341@att.com>
Change-Id: I15f0f12706bdaec766bbdcc0f8484c0d628787b8
(cherry picked from commit
4b9e44545bf817eac40810cb22aac1fa64dfee15)
nodeOpenRoadmVersion.equals(OpenroadmNodeVersion._71)
? Map.of(
// We don't need ODUC2, ODUC3 here, since they are handled in OTN service-path
nodeOpenRoadmVersion.equals(OpenroadmNodeVersion._71)
? Map.of(
// We don't need ODUC2, ODUC3 here, since they are handled in OTN service-path
- "ODU", List.of("ODU4", "ODUC4", "ODUFLEX"),
+ // This has to be in an order of deletion
+ "ODU", List.of("ODU4", "ODUFLEX", "ODUC4"),
// Add intermediate OTUCn rates (OTUC2, OTUC3)
// OTU4 is used in 100G service on 7.1 model
"other", List.of("OTU4", "OTUC2", "OTUC3", "OTUC4",
// Add intermediate OTUCn rates (OTUC2, OTUC3)
// OTU4 is used in 100G service on 7.1 model
"other", List.of("OTU4", "OTUC2", "OTUC3", "OTUC4",