This group is locked. No changes can be made to the group while it is locked.
Date
1 - 7 of 7
AAA Carbon Blocker Bugs
|
mike.cw.mccarthy@gmail.com
Based on our analysis, your project has Carbon Blocker Bug(s) that
require attention and action in the Carbon Simultaneous Release [0]. https://bugs.opendaylight.org/show_bug.cgi?id=8062 Bad padding in encrypted data If there are blocker bug(s) for Carbon, please provide an ETA for when they can be fixed. We kindly remind your project that the branches will be locked at RC1 scheduled for Thursday 4/20/2017 at 23:59 UTC Time [1]. For each Carbon Blocker Bug above, please choose an appropriate follow up: 1) Provide an ETA for a fix. 2) Downgrade the severity (SEVERITY=CRITICAL). 3) Retarget the bug for Carbon-SR1 or Nitrogen (ODL SR TARGET MILESTONE=NITROGEN). M [0] https://docs.google.com/spreadsheets/d/1VcB12FBiFV4GAEHZSspHBNxKI_9XugJp-6Qbbw20Omk/edit#gid=921315511 [1] https://wiki.opendaylight.org/view/Simultaneous_Release:Carbon_Release_Plan#Schedule |
|
|
|
Ryan Goulding <ryandgoulding@...>
1) Provide an ETA for a fix. Still determining root cause. We have an idea. This cannot be downgraded, and it cannot be retargeted. Will provide further updates as they become available. Thanks! Regards, Ryan Goulding On Wed, Apr 12, 2017 at 8:35 PM, Mike McCarthy <mike.cw.mccarthy@...> wrote: Based on our analysis, your project has Carbon Blocker Bug(s) that |
|
|
|
Mohamed ElSerngawy <melserngawy@...>
Hi all, It is not clear how to reproduce it, is there any procedures we can follow ? Thanks On Thu, Apr 13, 2017 at 9:27 AM, Ryan Goulding <ryandgoulding@...> wrote:
|
|
|
|
Colin Dixon <colin@...>
I don't think anyone who reported the bug is on this email. I'm CC'ing Robert, Tomas and Vratko since they have commented on the bug. --Colin On Thu, Apr 13, 2017 at 6:46 AM Mohamed ElSerngawy <melserngawy@...> wrote:
|
|
|
|
Ryan Goulding <ryandgoulding@...>
There is a link to this failing in NETCONF clustering CSIT [0]. Not sure whether this also happens in single node scenario as well. It would appear that when BP is instantiating the CertificateManagerService that a call which decrypts the keystore file location [1] is failing due to a PaddingException. If I had to guess, I would say that the leaf is probably an empty string... probably a race between the value being written initially (somewhere in the AAAEncryptionService instantation) and then read in the CertificateManagerService instantiation. On Thu, Apr 13, 2017 at 11:15 AM, Colin Dixon <colin@...> wrote:
|
|
|
|
Ryan Goulding <ryandgoulding@...>
Mohamed is taking a look into reproducing this since he was the one who most recently worked on the cert store / encryption code path. We will report back later. Regards, Ryan Goulding On Thu, Apr 13, 2017 at 11:56 AM, Ryan Goulding <ryandgoulding@...> wrote:
|
|
|
|
Colin Dixon <colin@...>
Thanks! --Colin On Thu, Apr 13, 2017 at 9:57 AM, Ryan Goulding <ryandgoulding@...> wrote:
|
|
|