[TRNSPRTPCE-668] Changing the operational state of a PortMapping should trigger a topology update Created: 27/May/22 Updated: 20/Sep/23 Resolved: 07/Jul/22 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Chlorine |
| Type: | Bug | Priority: | High |
| Reporter: | Jiao Thierry | Assignee: | Jiao Thierry |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 2 days | ||
| Original Estimate: | 2 days | ||
| Epic Link: | Demo SROL |
| Description |
|
Currently, any changes (AdminState and OperationalState) occurred in the PortMapping refreshes the topology. However, in some specific cases, the topology isn't refreshed. For instance, when only the OperationalState of PortMapping has been modified, A quick analysis and patch shall fix the issue. Acceptance criteria : the code does not bring regression, associated Junit tests are provided |