Hello An,

does this mean that the DLUX patches are free to go in?

Thanks,
Robert

On 2016-09-07 22:02, An Ho wrote:
The CONTROLLER/OPENFLOWPLUGIN team and other folks met to discuss the
status of this bug and the current plan of action is as follows:



1. TomP & CONTROLLER team will remove the invalid test(s) as per Bug
6659 [1].

   Deliverable: Patch(es) removing or fixing the tests.

2. The release team will schedule a respin of RC3.2 with the VBD fix at
9/7 23:59 UTC.

   Deliverable: Boron RC3.2 Common Karaf Disitrbution.

3. Luis & OPENFLOWPLUGIN team will run OFP tests a few more times.

   Deliverable: Comment on bugzilla [2] to confirm if we only get the
expected 26 failures in subsequent runs.

4. Anil & OPENFLOWPLUGIN team will attempt to reproduce locally in order
to establish if this is a real blocker.  We strongly recommend that the
team enable "debug" on some runs while trying to reproduce the bug.

   Deliverable: Comment on bugzilla [2] to confirm if Bug 6658 is a real
blocker.

5. Luis & OPENFLOWPLUGIN team will fix the tests that are failing
because of the change in behavior of candidate lists.

   Deliverable: Patch(es) fixing tests.



Best Regards,

An Ho



[1] https://bugs.opendaylight.org/show_bug.cgi?id=6659

[2] https://bugs.opendaylight.org/show_bug.cgi?id=6658





*From:*Colin Dixon [mailto:co...@colindixon.com]
*Sent:* Wednesday, September 07, 2016 10:35 AM
*To:* Abhijit Kumbhare
*Cc:* An Ho; controller-dev; rele...@lists.opendaylight.org;
openflowplugin-dev
*Subject:* Re: [openflowplugin-dev] [controller-dev] Regression in OF
cluster test



We're trying to figure that out, but if we could have somebody with
experience in OpenFlow plugin clustering give their 2 cents on if it's a
bug in the test or the behavior, that would really help.

Thanks,

--Colin



On Wed, Sep 7, 2016 at 1:33 PM, Abhijit Kumbhare <abhijitk...@gmail.com
<mailto:abhijitk...@gmail.com>> wrote:

Thanks Luis and An. If it is a test needing update rather than the code
- it might be better to keep Tom's fix.



On Wed, Sep 7, 2016 at 10:23 AM, An Ho <an...@huawei.com
<mailto:an...@huawei.com>> wrote:

    Still waiting to hear back from the controller team, but in the
    meantime I have created the following blocker bug [1] and updated
    the tracking spreadsheet.



    Hopefully after updating the tests there will not be any issues found.



    Best Regards,

    An Ho



    [1] https://bugs.opendaylight.org/show_bug.cgi?id=6658



    *From:*Luis Gomez [mailto:ece...@gmail.com <mailto:ece...@gmail.com>]
    *Sent:* Wednesday, September 07, 2016 10:07 AM
    *To:* An Ho
    *Cc:* controller-dev; openflowplugin-dev;
    rele...@lists.opendaylight.org
    <mailto:rele...@lists.opendaylight.org>; Tom Pantelis; Colin Dixon


    *Subject:* Re: Regression in OF cluster test



    So far I can see it mostly impacts entity-owner API behavior, so
    updating the test cases will fix most of the failures. I am counting
    1 day to update the test cases and run few times to see if there are
    other issues. If there is no issue after updating the test we can be
    ready by tomorrow, if there are issues after the test update I
    really doubt we can address them before Friday morning.



    BR/Luis





        On Sep 7, 2016, at 9:59 AM, An Ho <an...@huawei.com
        <mailto:an...@huawei.com>> wrote:



        Adding release mailing list since it may impact RC3



        Hi Tom Pantelis,



        Any comments regarding patch 45271.  Seems like it is changed
        the cluster behavior and that introduced regression in
        OpenFlowPlugin.  Would reverting be an option?



        Hi Luis,



        Is the impact confined to only CSIT test cases? Or does it
        affect end user regression of functionality as well?  In other
        words, would be sufficient to update the test cases?  Currently
        patch 45271 is related to blocker bug 6540 so reverting may be
        difficult.  Hypothetically, if the testing phase of RC3.2 will
        stretch to Friday morning, so would that be enough time to
        update the test cases and rerun the test?



        Best Regards,

        An Ho



        [1] https://git.opendaylight.org/gerrit/#/c/45271/

        [2] https://bugs.opendaylight.org/show_bug.cgi?id=6540







        *From:* Luis Gomez [mailto:ece...@gmail.com]
        *Sent:* Wednesday, September 07, 2016 9:49 AM
        *To:* controller-dev; openflowplugin-dev; An Ho
        *Subject:* Re: Regression in OF cluster test



        Most of the test regression seems to be related with
        entity-owner API behavior. Repair the test and retest everything
        is going to cost us one day, so should we go ahead or we revert
        the patch?



        BR/Luis





            On Sep 7, 2016, at 9:42 AM, Luis Gomez <ece...@gmail.com
            <mailto:ece...@gmail.com>> wrote:



            I am not sure this was intended (cluster behavior change)
            but this patch:



            https://git.opendaylight.org/gerrit/#/c/45271/



            introduced regression in the OpenFlow cluster test:



            
https://jenkins.opendaylight.org/releng/view/CSIT-3node/job/openflowplugin-csit-3node-clustering-only-boron/



            BR/Luis





    _______________________________________________
    controller-dev mailing list
    controller-...@lists.opendaylight.org
    <mailto:controller-...@lists.opendaylight.org>
    https://lists.opendaylight.org/mailman/listinfo/controller-dev




_______________________________________________
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
<mailto:openflowplugin-dev@lists.opendaylight.org>
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev





_______________________________________________
controller-dev mailing list
controller-...@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev

_______________________________________________
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Reply via email to