[BGPCEP-568] Be: unable to set password for tcpmd5 suite Created: 04/Oct/16 Updated: 03/Mar/19 Resolved: 04/Oct/16 |
|
| Status: | Resolved |
| Project: | bgpcep |
| Component/s: | General |
| Affects Version/s: | Bugzilla Migration |
| Fix Version/s: | Bugzilla Migration |
| Type: | Bug | ||
| Reporter: | Peter Gubka | Assignee: | Milos Fabian |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 6855 |
| Description |
|
the failure itself happens when: the responce is 500 .... the stack trace is long , but there is mentioned: etconfDocumentedException{message=RemoteDevice {controller-config}: Edit candidate failed: [RpcError [message=Test phase: {pcep-topology-provider={pcep-topology=Client password is not compatible with selected dispatcher}}, s |
| Comments |
| Comment by Vratko Polak [ 04/Oct/16 ] |
|
I believe this is just a consequence of Check_For_Bug_3753_Via_Bug_4267 test case failing to apply its workaround (due to a Robot code conflict). Here is a previous example of a step which is now skipped: As you see it configures config:modules/module/odl-pcep-impl-cfg:pcep-dispatcher-impl/global-pcep-dispatcher to use md5-channel-factory, without which "password" element is not considered compatible. |