[controller-dev] PATCH response not having the error details

Hi, I am using yang-patch to modify some of the leaf node values. But whenever the PATCH request fails, it is not giving the cause of the failure unlike the POST or PUT methods, but just gives an one-liner error that "canCommit encountered an unexpected failure". Is there any way in which the P

Re: [controller-dev] [Aaa-dev] [int/test] 401 from isolated cluster member?

My guess is it is failing the isAccessAllowed(...) test in the MDSALDynamicAuthorizationFilter. Will look a bit closer. Regards, Ryan Goulding On Thu, Apr 27, 2017 at 1:58 PM, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) wrote: > Hello AAA devs. > > > > I have a question, origin

[controller-dev] [int/test] 401 from isolated cluster member?

Hello AAA devs. I have a question, originally mentioned as a comment in a Bug ... I am unable to locate right now. Anyway, it is related to various bugs such as 7792 [1] and 8209 [2]. As more specific symptoms (8214 [3], 8062 [4]) are fixed now, I begin to suspect the 401 status is actually expec

[controller-dev] Timeout value of Cohert methods

Hi Tomas, Currently the canCommit() of DomDataTreeCohert will timeout in 5 seconds. How can this timeout value be increased ? Regards -Satish ___ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/l