+1, otherwise we can always grep for the offending features in the distribution
and remove them from the distribution-check.
> On Oct 25, 2017, at 7:14 AM, Tomas Cere -X (tcere - PANTHEON TECHNOLOGIES at
> Cisco) wrote:
>
> This is caused by some project that is still pulling
Vratko, I think we talked about this in the last integration call: if netconf
project (or any other) has 2 or more features that are incompatible (e.g.
produce SFT failures) but still required (e.g. for netconf device notifications
xor netconf cluster use case), the project should select 1 as
+unimgr-dev:
On Mon, Oct 23, 2017 at 6:02 PM, Vratko Polak -X (vrpolak - PANTHEON
TECHNOLOGIES at Cisco) wrote:
> Previous story: [2].
>
It's not that rare - just hit me again (on
https://git.opendaylight.org/gerrit/#/c/64674/), had to override once more
- and find this
Previous story: [2].
> who would have to do what
Ideally, Netconf developers would unify their features,
which does not seem to get done anytime soon [3].
There is a workaround in Int/Dist [4] prepared,
but it keeps SFT unstable, this time due to
(lack of) Karaf 4 memory efficiency [5].
+netconf-dev:
On Mon, Oct 23, 2017 at 3:24 PM, Tom Pantelis wrote:
> On Mon, Oct 23, 2017 at 8:41 AM, Michael Vorburger
> wrote:
>
>> Hello,
>>
>> Any idea who would have to do what to precent SFT from (only
>> occassionally?!) failing on
On Mon, Oct 23, 2017 at 8:41 AM, Michael Vorburger
wrote:
> Hello,
>
> Any idea who would have to do what to precent SFT from (only
> occassionally?!) failing on odl-integration-compatible-with-all due to
> ConflictingModificationAppliedException: Node was created by other
Hello,
Any idea who would have to do what to precent SFT from (only
occassionally?!) failing on odl-integration-compatible-with-all due to
ConflictingModificationAppliedException: Node was created by other
transaction, as seen on