[BGPCEP-954] ODL returns PCerror message for any PCreport message sent by PCC Created: 08/Jun/21 Updated: 10/Sep/21 Resolved: 10/Sep/21 |
|
| Status: | Resolved |
| Project: | bgpcep |
| Component/s: | PCEP |
| Affects Version/s: | Aluminium SR1 |
| Fix Version/s: | 0.16.4, Silicon SR3 |
| Type: | Bug | Priority: | Highest |
| Reporter: | kasi purushothaman | Assignee: | Olivier Dugeon |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Priority: | Highest | ||||||||
| Description |
|
ODL returns PCerror message for any PCreport message sent by PCC Version : Aluminium ----opendaylight-0.13.1 Steps:
Observation: pce(ODL) returns PCerror message on reception of PCreport message from pcc. Version : Aluminium ----opendaylight-0.13.1 |
| Comments |
| Comment by Robert Varga [ 21/Jul/21 ] |
|
Do you have karaf.log available from the run? It should contain a wee bit more information. |
| Comment by Olivier Dugeon [ 22/Jul/21 ] |
|
This is due to the order PCEP Objects are serialize by the PCC. In old draft, LSPA Object follow ERO while in RFC it follows RRO. We are working on this issue. A first solution has been proposed, but we are looking to a more generic approach to solve this issue and others that are similar. Indeed, we must be sufficiently flexible to handle PCC that follow RFC and those that follow old draft. |