Open Stack

On 09/16/2014 11:41 AM, Omri Marcovitch wrote:
> Hi all,
> 
> I would like to explain the problem we had: We saw comments of our CI in non-master branch without any jobs (logs).
> We filter the non-master branch so we should not supposed to run there so that was the reason we did not comments any jobs.
> 
> So why we comments in such a commits?
> Well, the issue was that we filter the master branch in the gerrit  filter (layout.yaml) and we assumed that it will be automatically will be filter from the zuul pipeline...but it was a mistake.
> Anyway we fixed this.
> 
> Thanks 
> Omri
> 
Thank you Omri.

This feature request has been created to help others avoid the same
problem in future: https://bugs.launchpad.net/zuul/+bug/1370105 Please
contribute to the creation of patches to implement this feature.

Your system is re-enabled. I look forward to seeing your results so that
I can confirm a link to browsable logs in your comments.

Thank you, Omri,
Anita.
> 
> 
> -----Original Message-----
> From: Omri Marcovitch [mailto:omrim at mellanox.com] 
> Sent: Monday, September 15, 2014 9:21 PM
> To: Announcements for third party CI operators.
> Subject: Re: [Third-party-announce] Mellanox CI is disabled, 4 comments per patchset
> 
> Hi Anita,
> 
> 1)   To prevent this issue I already created a "non-production zuul configuration", when we create a new CI machine the default zuul configuration will be the   
>         "non-production zuul configuration" which is not point to any openstack repositories, so only the main CI production server which is the single server with 
>           the zuul  openstack configuration  will be able to leave comment in openstack repos.
> 2)  Indeed there are no logs in this commit I will check it and fix this. 
> 
> Omri
> 
> 
> -----Original Message-----
> From: Anita Kuno [mailto:anteaya at anteaya.info]
> Sent: Monday, September 15, 2014 8:08 PM
> To: third-party-announce at lists.openstack.org
> Subject: Re: [Third-party-announce] Mellanox CI is disabled, 4 comments per patchset
> 
> On 09/15/2014 12:12 PM, Omri Marcovitch wrote:
>> Hi Anita,
>>
>> Thanks for your attention.
>>
>> This issue occur last night while we backup our deployment CI servers.
>> In some point of the backup process we had 4 CI servers that listen to zuul triggers and cause this issue.
>> Needless to say that as the backup process finished we validate that the zuul is disable in all of the reserve CI machines.
>>
>> Please re-enable our system again.
>>
>> Thanks
>> Omri
>>
> Hi Omri:
> 
> Tell me what you are going to do to prevent this from happening again in future.
> 
> Also I see a link to your wikipage in the comments your system leaves but no links to the logs of test artifacts.
> 
> from: http://ci.openstack.org/third_party.html#requirements
> Include a public link to all test artifacts to make debugging failed tests easier (using a dns name over a hardcoded ip is recommended). This should include:
> 
>     Environment details
>         This must include a utc timestamp of the test run
>     Test configuration
>         Skipped tests
>         logs should include a trace of the commands used
>     OpenStack logs
>     Tempest logs (including testr_results.html.gz)
>         logs must be browsable; logs requiring download, installation or login to access are not acceptable
> 
> Note
> 
> All test artifacts must be retained for one month.
> 
> So additionally ensure you have urls to test logs in your comments.
> 
> Let me know when this is accomplished.
> 
> Thank you Omri,
> Anita.
> 
>>
>> -----Original Message-----
>> From: Anita Kuno [mailto:anteaya at anteaya.info]
>> Sent: Monday, September 15, 2014 5:10 PM
>> To: third-party-announce at lists.openstack.org
>> Subject: [Third-party-announce] Mellanox CI is disabled, 4 comments 
>> per patchset
>>
>> https://review.openstack.org/#/c/114328/
>>
>> 9732 mellanox Mellanox CI mlnx-openstack-ci at dev.mellanox.co.il
>>
>> Mellanox CI commented 4 times on the above patchset and the account has been disabled.
>>
>> Please evaluate your system so that it meets all stated requirements, including the one comment per patchset requirement:
>> http://ci.openstack.org/third_party.html#requirements
>>
>> Once you are confident you meet all requirements for your system you may request having it re-enabled, either as a reply to this post or on irc in the #openstack-infra channel.
>>
>> Thank you,
>> Anita.
>>
>> _______________________________________________
>> Third-party-announce mailing list
>> Third-party-announce at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announ
>> ce
>>
>> _______________________________________________
>> Third-party-announce mailing list
>> Third-party-announce at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announ
>> ce
>>
> 
> 
> _______________________________________________
> 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
>