Open Stack

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