An,
We discovered the root cause of this problem today, with the help of
Robert, while investigating a failing Boron SFC Integration test.
Originally I wanted to fix this bug in Boron RC3 and marked the bug as
so, but after talking to Jamo, he said it would be ok to fix in Boron
SR1 without causing the SFC features to be marked experimental as long
as we link the test failure to the bug.
The fix is very simple, and the patch [0] has already been merged in
Carbon/master. Considering SFC has a blocker bug fix coming tomorrow
morning GMT+1, I could cherry-pick this [0] to stable/boron if you're ok
with that. Otherwise the test will still fail, but be linked to a bug
until Boron SR1.
Regards,
Brady
[0] https://git.opendaylight.org/gerrit/#/c/45233/
On 06/09/16 19:25, An Ho wrote:
Hi Robert, Brady,
During the MDSAL call, some concerns were raised as to whether Bug
6648 is a blocking issue in the Boron release. However, the bugzilla
note for the bug indicates it a “normal” with a target of “Boron-SR1”
in October. Could we get some clarity on the priority and target for
this bug. Is it a true blocker that must be fixed before Boron is
released?
Best Regards,
An Ho
_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev
