This group is locked. No changes can be made to the group while it is locked.
Date
1 - 10 of 10
Bug 8682 - Unable to find a matching constructor on class org.opendaylight.aaa.idm.AaaIdmLight for arguments
|
Michael Vorburger <vorburger@...>
On Tue, Jun 13, 2017 at 5:25 PM, Ryan Goulding <ryandgoulding@...> wrote:
Hereby confirming that with this revert (locally mvn install'd) the https://bugs.opendaylight.org/show_bug.cgi?id=8682 does (obviously) not occur anymore - thanks for the revert.
Just FYI, it did occur consistently on the Karaf 4 dist built in genius project.. on every start & feature install. I can't quite explain how this problem could be project specific though.
|
|
|
|
Ryan Goulding <ryandgoulding@...>
Reverted to unblock. Look out for the new artifact after the merge build. Sorry for any inconvenience... appears to be an intermittent issue. Regards, Ryan Goulding On Tue, Jun 13, 2017 at 11:14 AM, Michael Vorburger <vorburger@...> wrote:
|
|
|
|
Michael Vorburger <vorburger@...>
On Tue, Jun 13, 2017 at 5:11 PM, Ryan Goulding <ryandgoulding@...> wrote:
I'm trying to understand it right now...
|
|
|
|
Ryan Goulding <ryandgoulding@...>
Michael, do you have any other ideas? you commented that you only see this in genius; is the feature installation drastically different than other features? I am willing to merge the revert to unblock genius, but would also appreciate an understanding of why this is occurring only in genius. Regards, Ryan Goulding On Tue, Jun 13, 2017 at 11:07 AM, Mohamed El-Serngawy <m.elserngawy@...> wrote:
|
|
|
|
Mohamed ElSerngawy
I cannot reproduce the issue it works fine and if I upgrade aaa-karaf to karaf4 to test a lot of other issues show up. May it because the new artifact idm-config.xml not present yet (not really sure). Michael, if you have any thoughts what could be the cause let us know. Otherwise Ryan you can revert it, I don't have more time to spend on that. BR On Tue, Jun 13, 2017 at 10:26 AM, Ryan Goulding <ryandgoulding@...> wrote:
|
|
|
|
Ryan Goulding <ryandgoulding@...>
Can we merge the revert? I want to unblock this issue. I am more than happy to keep the queue of incoming patches clear so you can avoid rebases... let me know what you want to do, Mohamed. Thanks! Regards, Ryan Goulding On Tue, Jun 13, 2017 at 10:03 AM, Ryan Goulding <ryandgoulding@...> wrote:
|
|
|
|
Ryan Goulding <ryandgoulding@...>
Sounds like a race condition. Regards, Ryan Goulding On Tue, Jun 13, 2017 at 10:01 AM, Mohamed El-Serngawy <m.elserngawy@...> wrote:
|
|
|
|
Mohamed ElSerngawy
Hi, Well, I saw this once at the patch [1] (set 3 or 4) but didn't show up again till we merge it. I don't think reverting the patch will solve the issue, later or sooner we need to merged it. give me sometimes Ryan to look to it. BR On Tue, Jun 13, 2017 at 9:05 AM, Ryan Goulding <ryandgoulding@...> wrote:
|
|
|
|
Ryan Goulding <ryandgoulding@...>
Strange... this passed jenkins-releng and appeared to work. Caused by a patch that was merged yesterday, revert is here [0]. On Tue, Jun 13, 2017 at 9:00 AM, Michael Vorburger <vorburger@...> wrote:
|
|
|
|
Michael Vorburger <vorburger@...>
Team AAA, are you already aware of https://bugs.opendaylight.org/show_bug.cgi?id=8682, and perhaps have a fix? |
|
|