Re: [OpenStack-Infra] Request to enable IBM-GPFS-CINDER-CI account
Thanks Clark for clearing the confusion about accounts. We are planning to use Gerrit account with Gerrit ID of 12491 (username : ibm-gpfs-ci) Please delete the other account (Gerrit ID : 21058). The above mentioned gerrit id was created long back. Could you please make changes to the account so that we can login to gerrit using the email id as mentioned below. Currently, when we try to login to gerrit, it takes us to Ubuntu One page and when we enter credentials, it says account with the email not found. Username : ibm-gpfs-ci Full Name : IBM GPFS CI Email Address : rsand...@in.ibm.com Thanks, Digvijay From: Clark Boylan To: Digvijay B Ukirde/India/IBM@IBMIN, Mikhail Medvedev Cc: Jay S Bryant , OpenStack Infra Date: 03/21/2016 11:53 PM Subject:Re: [OpenStack-Infra] Request to disable IBM-GPFS-CINDER-CI account temparary On Mon, Mar 21, 2016, at 03:52 AM, Digvijay B Ukirde wrote: > > Hi Mikhail, > > Currently IBM-GPFS-CINDER-CI is facing some internal issue because of > which > it is resulting negative report in CI dashboard. > We are trying to disable our cinder-ci but some other server(older ci > setup) is taking patches because of which we are unable to disable the > CI > or may be Gerrit cache is the issue (We are not sure about it) > > Since, > We noticed that there are two recheck keywords for IBM GPFS CI in Cinder. > One is recheck-gpfs and the result always shows NOT_REGISTERED. > One is recheck ibmgpfs and the result is always good. [ this is in our ci > setup - layout.yaml ] > > > So till we fix the issue can you please disable the IBM-GPFS-CINDER-CI > account. > > Once we fix the issue we will get back to you. There are two "IBM GPFS CI" accounts with the same email address of rsand...@in.ibm.com. They have Gerrit IDs of 12491 (username ibm-gpfs-ci) and 21058 (no username). Neither of these accounts have the indicated username and I have not been able to find an account with that username or Full Name. I have disabled both of the accounts listed above that I was able to find. When you get things working again you will need to specify which account is being used so that we only enable the one that you intend on using. Clark ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Request to disable IBM-GPFS-CINDER-CI account temparary
Hi Mikhail, Currently IBM-GPFS-CINDER-CI is facing some internal issue because of which it is resulting negative report in CI dashboard. We are trying to disable our cinder-ci but some other server(older ci setup) is taking patches because of which we are unable to disable the CI or may be Gerrit cache is the issue (We are not sure about it) Since, We noticed that there are two recheck keywords for IBM GPFS CI in Cinder. One is recheck-gpfs and the result always shows NOT_REGISTERED. One is recheck ibmgpfs and the result is always good. [ this is in our ci setup - layout.yaml ] So till we fix the issue can you please disable the IBM-GPFS-CINDER-CI account. Once we fix the issue we will get back to you. Regards, Digvijay ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [Third-party CI] - Running CI setup failing due to NOT_REGISTERED issue
Hi Mikhail,
> Search your zuul logs for NOT_REGISTERED for clues
although there are not many statement with NOT_REGISTERED in it..
pasting relevant part : http://paste.openstack.org/show/490634/
> I have noticed that you are voting, and reporting on cinder.
I was not aware of these restrictions & was trying to check whether I am
able to trigger patch by comment.
I will take precaution now onwards.
Thanks,
Digvijay
From: Mikhail Medvedev
To: Digvijay B Ukirde/India/IBM@IBMIN
Cc: "openstack-infra@lists.openstack.org"
Date: 03/16/2016 03:43 AM
Subject:Re: [OpenStack-Infra] [Third-party CI] - Running CI setup
failing due to NOT_REGISTERED issue
Digvijay,
I can not see anything obviously wrong with your configuration yet to cause
NOT_REGISTERED. Your check pipeline does use dsvm-tempest-full job, and
there is a build with that name registered on gearman. Search your zuul
logs for NOT_REGISTERED for clues, and post relevant parts to
http://paste.openstack.org/.
But I have noticed that you are voting, and reporting on cinder. Did you
ask cinder devs if it is ok to start posting comments? Otherwise, please
disable reports until your CI becomes reasonably stable. Use
openstack-dev/ci-sandbox project to test your CI. You should remove/comment
out the following from check pipeline in zuul layout:
success:
gerrit:
{}
failure:
gerrit:
{}
merge-failure:
gerrit: {}
---
Mikhail
On Tue, Mar 15, 2016 at 2:00 AM, Digvijay B Ukirde <
digvijay.uki...@in.ibm.com> wrote:
Hi Mikhail,
Thanks for quick response.
> It would be useful if you could paste your zuul pipeline
> configuration. It shows up in zuul.log when you restart zuul-serve
2016-03-15 12:14:00,482 INFO zuul.Gerrit: Updating information for
292730,1
2016-03-15 12:14:11,903 INFO zuul.Gerrit: Updating information for
282392,10
2016-03-15 12:14:21,520 INFO zuul.Server: Starting scheduler
2016-03-15 12:14:21,543 INFO zuul.IndependentPipelineManager: Configured
Pipeline Manager check
2016-03-15 12:14:21,543 INFO zuul.IndependentPipelineManager: Source:
2016-03-15 12:14:21,543 INFO zuul.IndependentPipelineManager:
Requirements:
2016-03-15 12:14:21,543 INFO zuul.IndependentPipelineManager: Events:
2016-03-15 12:14:21,543 INFO zuul.IndependentPipelineManager:
2016-03-15 12:14:21,544 INFO zuul.IndependentPipelineManager:
2016-03-15 12:14:21,544 INFO zuul.IndependentPipelineManager:
2016-03-15 12:14:21,544 INFO zuul.IndependentPipelineManager:
2016-03-15 12:14:21,544 INFO zuul.IndependentPipelineManager: Projects:
2016-03-15 12:14:21,544 INFO zuul.IndependentPipelineManager:
openstack/cinder
2016-03-15 12:14:21,544 INFO zuul.IndependentPipelineManager:
2016-03-15 12:14:21,544 INFO zuul.IndependentPipelineManager: On start:
2016-03-15 12:14:21,545 INFO zuul.IndependentPipelineManager: []
2016-03-15 12:14:21,545 INFO zuul.IndependentPipelineManager: On success:
2016-03-15 12:14:21,545 INFO zuul.IndependentPipelineManager: ,
{'verified': 1}>
2016-03-15 12:14:21,545 INFO zuul.IndependentPipelineManager: On failure:
2016-03-15 12:14:21,545 INFO zuul.IndependentPipelineManager: ,
{'verified': -1}>
2016-03-15 12:14:21,545 INFO zuul.IndependentPipelineManager: On
merge-failure:
2016-03-15 12:14:21,545 INFO zuul.IndependentPipelineManager: ,
{'verified': -1}>
2016-03-15 12:14:21,545 INFO zuul.IndependentPipelineManager: Configured
Pipeline Manager silent
2016-03-15 12:14:21,546 INFO zuul.IndependentPipelineManager: Source:
2016-03-15 12:14:21,546 INFO zuul.IndependentPipelineManager:
Requirements:
2016-03-15 12:14:21,546 INFO zuul.IndependentPipelineManager: Events:
2016-03-15 12:14:21,546 INFO zuul.IndependentPipelineManager:
2016-03-15 12:14:21,546 INFO zuul.IndependentPipelineManager:
2016-03-15 12:14:21,546 INFO zuul.IndependentPipelineManager:
2016-03-15 12:14:21,546 INFO zuul.IndependentPipelineManager: Projects:
2016-03-15 12:14:21,546 INFO zuul.IndependentPipelineManager: On start:
2016-03-15 12:14:21,547 INFO zuul.IndependentPipelineManager: []
2016-03-15 12:14:21,547 INFO zuul.IndependentPipelineManager: On success:
2016-03-15 12:14:21,547 INFO zuul.IndependentPipelineManager: []
2016-03-15 12:14:21,547 INFO zuul.IndependentPipelineManager: On failure:
2016-03-15 12:14:21,547 INFO zuul.IndependentPipelineManager: []
2016-03-15 12:14:21,547 INFO zuul.Indepen
Re: [OpenStack-Infra] [Third-party CI] - Running CI setup failing due to NOT_REGISTERED issue
erritEventConnector: Received
unrecognized event type 'ref-replicated' from Gerrit.
Can not get account information.
> NOT_REGISTERED means that there is mismatch between the job zuul wants
> to start, and what jenkins registered (if it did) with zuul gearman
> server. Check what got registered on gearman server with:
> echo status | nc 4730 # assuming you use standard
> port, and gearman is on zuul
root@master:~# echo status | nc 4730
build:dsvm-tempest-full 2 0 0
zuul:enqueue0 0
1
zuul:promote0 0
1
merger:update 0 0
1
stop:master.in.ibm.com 0 0 1
build:dsvm-tempest-full:devstack_slave 0 0 0
zuul:get_running_jobs 0 0 1
build:noop-check-communication 0 0 2
build:noop-check-communication:master 0 0 2
set_description:master.in.ibm.com 0 0 1
merger:merge0 0
1
.
What is wrong with the configuration?
Thanks,
Digivjay
From: Mikhail Medvedev
To: Digvijay B Ukirde/India/IBM@IBMIN
Cc: "openstack-infra@lists.openstack.org"
Date: 03/14/2016 08:12 PM
Subject:Re: [OpenStack-Infra] [Third-party CI] - Running CI setup
failing due to NOT_REGISTERED issue
Hi Gigvijay,
On Mon, Mar 14, 2016 at 7:00 AM, Digvijay B Ukirde
wrote:
> Hi Team,
>
> I am running zuul, zuul merger and Jenkins in one Ubuntu.
> I have configured zuul and zuul merger, Test connection for Jenkins
gearman
> plugin also runs successfully.
>
> But whenever patch come, CI is building job dsvm-tempest-full with
> NOT_REGISTERED result at start before it actually get processed by CI.
> So when it actually go through the CI, it gives result with SUCCESS but
with
> 1 recheck.
It would be useful if you could paste your zuul pipeline
configuration. It shows up in zuul.log when you restart zuul-server.
NOT_REGISTERED means that there is mismatch between the job zuul wants
to start, and what jenkins registered (if it did) with zuul gearman
server. Check what got registered on gearman server with:
echo status | nc 4730 # assuming you use standard
port, and gearman is on zuul
Would be helpful if you paste that as well.
>
> Besides when I checked my logs [debug.log] my Gearman is working fine
> DEBUG zuul.Gearman: Function build:dsvm-tempest-full is registered
> while I am getting error of Gerrit
> ERROR zuul.GerritEventConnector: Received unrecognized event type
> 'ref-replicated' from Gerrit. Can not get account information.
>
Ignore that error.
> If you know this issue with solution, can you please help me.
>
>
>
> Thanks,
> Digvijay
>
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] [Third-party CI] - Running CI setup failing due to NOT_REGISTERED issue
Hi Team, I am running zuul, zuul merger and Jenkins in one Ubuntu. I have configured zuul and zuul merger, Test connection for Jenkins gearman plugin also runs successfully. But whenever patch come, CI is building job dsvm-tempest-full with NOT_REGISTERED result at start before it actually get processed by CI. So when it actually go through the CI, it gives result with SUCCESS but with 1 recheck. Besides when I checked my logs [debug.log] my Gearman is working fine DEBUG zuul.Gearman: Function build:dsvm-tempest-full is registered while I am getting error of Gerrit ERROR zuul.GerritEventConnector: Received unrecognized event type 'ref-replicated' from Gerrit. Can not get account information. If you know this issue with solution, can you please help me. Thanks, Digvijay ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
