<div dir="ltr">Hi Anita, <div><br></div><div>I think I knew what happened, we had a power failure this weekend, and the VM that was running the Jenkins master for this CI was automatically booted, if you see on the CI reports all of then where sent on 13/07. </div><div><br></div><div>Whats is there any criteria for removing CIs? I fell this removal was very unfair. I have seen CIs reporting errors for weeks and then, only after warnings to operators in this mailing list, they are removed. In our case, it was less than 24h, we got no warnings and got this account disabled. Today, we can't test the CI against the patch that entered (yesterday) and will have to do all the process to get the account again. Is it possible to re-enable the account so we can continue the process to test the patch that should fix the problem?</div><div><br></div><div>Thanks,</div><div>Erlon</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 14, 2015 at 12:06 PM, Anita Kuno <span dir="ltr"><<a href="mailto:anteaya@anteaya.info" target="_blank">anteaya@anteaya.info</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 07/14/2015 10:18 AM, Erlon Cruz wrote:<br>
> Hi Anita,<br>
><br>
> There was a change in an external library (lockutils) that was causing the<br>
> patches run in our CI to fail. We have reported the problem[1], submitted a<br>
> fix[2], and shut down the CI while the fix wasn't merged.<br>
<br>
</span>Okay well somehow you shut down your system but it was still leaving<br>
comments on gerrit patches. How did that happen?<br>
<br>
Thanks Erlon,<br>
Anita.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
> That was about 10<br>
> days ago, and the patch only landed yesterday. We will re-run the above<br>
> tests and submit the successful results.<br>
><br>
> [1] <a href="https://bugs.launchpad.net/cinder/+bug/1470112" rel="noreferrer" target="_blank">https://bugs.launchpad.net/cinder/+bug/1470112</a><br>
> [2] <a href="https://review.openstack.org/#/c/197686/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/197686/</a><br>
><br>
> On Mon, Jul 13, 2015 at 7:06 PM, Anita Kuno <<a href="mailto:anteaya@anteaya.info">anteaya@anteaya.info</a>> wrote:<br>
><br>
>> <a href="https://review.openstack.org/#/c/199537/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/199537/</a><br>
>><br>
>> <a href="https://review.openstack.org/#/c/198853/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/198853/</a><br>
>><br>
>> <a href="https://review.openstack.org/#/c/193937/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/193937/</a><br>
>><br>
>> <a href="https://review.openstack.org/#/c/201241/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/201241/</a><br>
>><br>
>> This account is posting NOT_REGISTERED on patches.<br>
>><br>
>> This is an indication that zuul (if you are using zuul) is unable to<br>
>> clearly communicate with Jenkins nodes. This is an internal error and<br>
>> has nothing to do with the patch.<br>
>><br>
>> Please fix your system and post your incident report with details as a<br>
>> response.<br>
>><br>
>> Please test your system on ci-sandbox after it is working again.<br>
>><br>
>> Thank you,<br>
>> Anita.<br>
>><br>
>> _______________________________________________<br>
>> Third-party-announce mailing list<br>
>> <a href="mailto:Third-party-announce@lists.openstack.org">Third-party-announce@lists.openstack.org</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce</a><br>
>> Please attend the third party meetings:<br>
>> <a href="http://eavesdrop.openstack.org/#Third_Party_Meeting" rel="noreferrer" target="_blank">http://eavesdrop.openstack.org/#Third_Party_Meeting</a><br>
>><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Third-party-announce mailing list<br>
> <a href="mailto:Third-party-announce@lists.openstack.org">Third-party-announce@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce</a><br>
> Please attend the third party meetings: <a href="http://eavesdrop.openstack.org/#Third_Party_Meeting" rel="noreferrer" target="_blank">http://eavesdrop.openstack.org/#Third_Party_Meeting</a><br>
><br>
<br>
<br>
_______________________________________________<br>
Third-party-announce mailing list<br>
<a href="mailto:Third-party-announce@lists.openstack.org">Third-party-announce@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce</a><br>
Please attend the third party meetings: <a href="http://eavesdrop.openstack.org/#Third_Party_Meeting" rel="noreferrer" target="_blank">http://eavesdrop.openstack.org/#Third_Party_Meeting</a><br>
</div></div></blockquote></div><br></div>