[Third-party-announce] OpenDaylight CI Failing

Anita Kuno anteaya at anteaya.info
Wed Dec 3 16:49:50 UTC 2014


On 12/02/2014 07:02 PM, Edgar Magana wrote:
> Is there anyone objecting about enabling ODL CI?
> I am not and I give +2 to re-enable it.
> 
> Edgar
The account has been re-enabled. Thank you, Edgar for helping Andrew to
work though this issue.

Thanks,
Anita.
> 
> On 12/2/14, 12:15 PM, "Andrew Grimberg" <agrimberg at linuxfoundation.org>
> wrote:
> 
>> My apologies on that front. Hopefully we won't run into this sort of
>> situation again either and I won't be tempted ;)
>>
>> I've switched our CI back to the standard credentials, but until our
>> account is reactivated it can't talk to Gerrit.
>>
>> -Andy-
>>
>> On Tue, 2014-12-02 at 19:36 +0000, Edgar Magana wrote:
>>> Anita,
>>>
>>> Ok, I understand it now.
>>>
>>> Please Andrew, do not do it ever again.
>>>
>>> Team,
>>>
>>> It seems that ODL CI is stable and it has my vote to be re-enabled.
>>>
>>> Thanks,
>>>
>>> Edgar
>>>
>>> On 12/2/14, 11:26 AM, "Anita Kuno" <anteaya at anteaya.info> wrote:
>>>
>>>> On 12/02/2014 02:18 PM, Edgar Magana wrote:
>>>>> Andrew,
>>>>>
>>>>> There is something still wrong with OpenDaylight CI.
>>>>> I reviewed the latest jenkins jobs where it passed:
>>>>> https://review.openstack.org/#/c/137493/
>>>>>
>>>>> And it seems that CI is fine but it is reporting in gerrit under your
>>>>> name
>>>>> instead of OpenDaylight CI.
>>>>>
>>>>> For instance, if you see: https://review.openstack.org/#/c/113339/
>>>>>
>>>>> All the way until Patch 4, the logs were reported as OpenDaylight CI
>>> but
>>>>> after patch 5 (probably when you introduced your latest changes) it
>>> is
>>>>> now
>>>>> reporting as Andrew Grimberg
>>>>>
>>>>> Please, modify it.
>>>> Edgar:
>>>>
>>>> He made that change to demonstrate CI fitness when his system was
>>>> disabled. I was only meant for that means and should not be reporting
>>> on
>>>> patches as Andrew Grimberg.
>>>>
>>>> If this is the only blocker, please let me know so we can re-enable the
>>>> account.
>>>>
>>>> Using your personal account to demonstrate CI fitness should never be
>>>> used to comment on patches. You should only use the new ci-sandbox repo
>>>> or the patches Edgar has for testing cis.
>>>>
>>>> Thank you,
>>>> Anita.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Edgar
>>>>>
>>>>> On 12/2/14, 10:04 AM, "Andrew Grimberg"
>>> <agrimberg at linuxfoundation.org>
>>>>> wrote:
>>>>>
>>>>>> Greetings folks,
>>>>>>
>>>>>> Just trying to get this loop closed off so that I can switch our CI
>>>>>> back
>>>>>> to the proper key for doing validation. Is there anything we still
>>> need
>>>>>> to do to get the rights turned back on?
>>>>>>
>>>>>> -Andy-
>>>>>>
>>>>>> On Mon, 2014-11-24 at 16:05 +0000, Edgar Magana wrote:
>>>>>>> Please, see my comments about the patch. We can continue the
>>>>>>> communication
>>>>>>> on gerrit.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Edgar
>>>>>>>
>>>>>>> On 11/24/14, 7:45 AM, "Kyle Mestery" <mestery at mestery.com> wrote:
>>>>>>>
>>>>>>>> Copying Andy as well.
>>>>>>>>
>>>>>>>> On Mon, Nov 24, 2014 at 9:44 AM, Kyle Mestery
>>> <mestery at mestery.com>
>>>>>>> wrote:
>>>>>>>>> On Fri, Nov 21, 2014 at 1:45 PM, Edgar Magana
>>>>>>>>> <edgar.magana at workday.com> wrote:
>>>>>>>>>> Andy and Kyle,
>>>>>>>>>>
>>>>>>>>>> Once the patch [1] is merged, we can re-verify ODL CI and then
>>>>>>> deciding
>>>>>>>>>> about the re-enable part.
>>>>>>>>>> At this moment ODL CI is even failing for your patch.
>>>>>>>>>>
>>> https://jenkins.opendaylight.org/ovsdb/job/openstack-gerrit/2782/
>>>>>>>>>>
>>>>>>>>> Edgar, the patch in question is now passed, we fixed the issues
>>> with
>>>>>>>>> the CI now. Can you remove your -1 on the devstack patch [1]?
>>> Once
>>>>>>>>> htat merges, I think we're good to go to re-enable now.
>>>>>>>>>
>>>>>>>>> Thank you!
>>>>>>>>> Kyle
>>>>>>>>>
>>>>>>>>> [1] https://review.openstack.org/#/c/134309/
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>> Edgar
>>>>>>>>>>
>>>>>>>>>> On 11/21/14, 9:31 AM, "Kyle Mestery" <mestery at mestery.com>
>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> On Fri, Nov 21, 2014 at 11:30 AM, Edgar Magana
>>>>>>>>>>> <edgar.magana at workday.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>> This is bothering me about the tests results:
>>>>>>>>>>>>
>>>>>>>
>>>>>>>>>>>>
>>>
>>>>>>>>>>>> https://jenkins.opendaylight.org/ovsdb/job/openstack-gerrit/2806
>>>>>>>>>>>> /a
>>>>>>>>>>>> rt
>>>>>>>>>>>> if
>>>>>>>>>>>> act
>>>>>>>>>>>> /o
>>>>>>>>>>>> dl_tempest_test_list.txt
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> The status is PASSED when this show a test failed!
>>>>>>>>>>>>
>>>>>>>>>>> Agreed, this is fixed with the more recent version of
>>> OpenDaylight
>>>>>>>>>>> (Helium.1), which I have a patch up for here [1].
>>>>>>>>>>>
>>>>>>>>>>> Still, this is worth noting.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Kyle
>>>>>>>>>>>
>>>>>>>>>>> [1] https://review.openstack.org/#/c/134309/
>>>>>>>>>>>
>>>>>>>>>>>> Edgar
>>>>>>>>>>>>
>>>>>>>>>>>> On 11/21/14, 9:19 AM, "Andrew Grimberg"
>>>>>>>>>>>> <agrimberg at linuxfoundation.org>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, 2014-11-21 at 17:16 +0000, Doug Wiegley wrote:
>>>>>>>>>>>>>>> On Nov 21, 2014, at 9:57 AM, Andrew Grimberg
>>>>>>>>>>>>>> <agrimberg at linuxfoundation.org> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Fri, 2014-11-21 at 16:44 +0000, Doug Wiegley wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I checked out their CI results, and it's behaving well
>>> enough
>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>> gerrit access shouldn't be harmful.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The test build can be seen off of this review:
>>>>>>>>>>>>>>>> https://review.openstack.org/#/c/136142/
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The only real issue that I saw was that the results link
>>>>>>>>>>>>>> doesn't go
>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>> a logs directory as defined here:
>>>>>>>>>>>>>>>>
>>>>>>>
>>>>>>>>>>>>>>
>>>
>>>>>>>>>>>>>> https://wiki.openstack.org/wiki/NeutronThirdPartyTesting#Log_.
>>>>>>>>>>>>>> 26
>>>>>>>>>>>>>> _T
>>>>>>>>>>>>>> es
>>>>>>>>>>>>>> t_R
>>>>>>>>>>>>>> es
>>>>>>>>>>>>>> ults_Filesystem_Layout
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Doug,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks for the link. If the current logs tarball was
>>> exploded
>>>>>>> out
>>>>>>>>>>>>>>> directly on the Jenkins archive links would that be better?
>>>>>>> Kyle,
>>>>>>>>>>>>>> you
>>>>>>>>>>>>>>> may want to consider modifying the final log archival
>>>>>>>>>>>>>> composition of
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>> job.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I think the common thing to do is to have a post-build step
>>>>>>>>>>>>>> that
>>>>>>>>>>>>>> dumps
>>>>>>>>>>>>>> your artifacts onto a generic web server somewhere, with
>>>>>>> on-the-fly
>>>>>>>>>>>>>> decompression enabled if you want to store .gz's, and then
>>> link
>>>>>>> to
>>>>>>>>>>>>>> that
>>>>>>>>>>>>>> directory in gerrit, instead of linking to jenkins.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> For example, this:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>
>>>>>>>>>>>>>>
>>>
>>>>>>>>>>>>>> http://jenkins.a10cloud.com/job/a10-neutron-tempest/lastSucces
>>>>>>>>>>>>>> sf
>>>>>>>>>>>>>> ul
>>>>>>>>>>>>>> Bu
>>>>>>>>>>>>>> ild
>>>>>>>>>>>>>> /
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ... becomes a link to this:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>> http://ci.a10cloud.com/logs/a10-neutron-tempest/136248/7/5114/
>>>>>>>>>>>>>
>>>>>>>>>>>>> We're definitely working towards that. Haven't managed to get
>>>>>>>>>>>>> everything
>>>>>>>>>>>>> in place to handle it though :-/
>>>>>>>>>>>>>
>>>>>>>>>>>>> Then again, outside of our integration with OpenStack we
>>> haven't
>>>>>>> had
>>>>>>>>>>>>> a
>>>>>>>>>>>>> lot of call for that since our Jenkins is open to the world
>>> to
>>>>>>>>>>>>> see
>>>>>>>>>>>>> including how the jobs are configured.
>>>>>>>>>>>>>
>>>>>>>>>>>>> -Andy-
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Andrew J Grimberg
>>>>>>>>>>>>> Systems Administrator
>>>>>>>>>>>>> The Linux Foundation
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> Third-party-announce mailing list
>>>>>>>>>>>> Third-party-announce at lists.openstack.org
>>>>>>>>>>>>
>>>>>>>
>>>>>>>>>>>>
>>>
>>>>>>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-
>>>>>>>>>>>> an
>>>>>>>>>>>> no
>>>>>>>>>>>> un
>>>>>>>>>>>> ce
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Third-party-announce mailing list
>>>>>>>>>>> Third-party-announce at lists.openstack.org
>>>>>>>
>>>>>>>>>>>
>>>
>>>>>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-a
>>>>>>>>>>> nn
>>>>>>>>>>> ou
>>>>>>>>>>> nc
>>>>>>>>>>> e
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Third-party-announce mailing list
>>>>>>>>>> Third-party-announce at lists.openstack.org
>>>>>>>>>>
>>>>>>>
>>>>>>>>>>
>>>
>>>>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-an
>>>>>>>>>> no
>>>>>>>>>> un
>>>>>>>>>> ce
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Third-party-announce mailing list
>>>>>>>> Third-party-announce at lists.openstack.org
>>>>>>>
>>>>>>>>
>>>
>>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-anno
>>>>>>>> un
>>>>>>>> ce
>>>>>>>
>>>>>>
>>>>>> -- 
>>>>>> Andrew J Grimberg
>>>>>> Systems Administrator
>>>>>> The Linux Foundation
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Third-party-announce mailing list
>>>>> Third-party-announce at lists.openstack.org
>>>>>
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Third-party-announce mailing list
>>>> Third-party-announce at lists.openstack.org
>>>
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce
>>>
>>>
>>> _______________________________________________
>>> Third-party-announce mailing list
>>> Third-party-announce at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce
>>
>> -- 
>> Andrew J Grimberg
>> Systems Administrator
>> The Linux Foundation
> 
> 
> _______________________________________________
> Third-party-announce mailing list
> Third-party-announce at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce
> 




More information about the Third-party-announce mailing list