Re: [OpenStack-Infra] [Third-party CI] - Running CI setup failing due to NOT_REGISTERED issue

2016-03-19 Thread Mikhail Medvedev
On Wed, Mar 16, 2016 at 12:01 AM, Digvijay B Ukirde
<digvijay.uki...@in.ibm.com> wrote:
>
> 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/

Is there anything interesting in the log before the error?

>
>
> > 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.

Make sure you read and follow guidelines for third-party CIs at
http://docs.openstack.org/infra/system-config/third_party.html#requirements

>
>
> Thanks,
> Digvijay
> Mikhail Medvedev ---03/16/2016 03:43:36 AM---Digvijay, I can not see anything 
> obviously wrong with your configuration yet to cause
>
> From: Mikhail Medvedev <mihail...@gmail.com>
> To: Digvijay B Ukirde/India/IBM@IBMIN
> Cc: "openstack-infra@lists.openstack.org" 
> <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:  types: patchset-created>
> 2016-03-15 12:14:21,544 INFO zuul.IndependentPipelineManager:  types: change-restored>
> 2016-03-15 12:14:21,544 INFO zuul.IndependentPipelineManager:  types: comment-added comments: (?i)^(Patch Set [0-9]+:)?( 
> [\w\\+-]*)*(\n\n)?\s*recheck(( (?:bug|lp)[\s#:]*(\d+))|( no bug))\s*gt;
> 2016-03-15 12:14:21,544 INFO zuul.IndependentPipelineManager:  types: comment-added comments: (?i)^(Patch Set [0-9]+:)?( 
> [\w\\+-]*)*(\n\n)?\s*recheck(( (?:bug|lp)[\s#:]*(\d+))|( ibmgpfs))\s*gt;
> 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:  dsvm-tempest-full>
> 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 IN

Re: [OpenStack-Infra] [Third-party CI] - Running CI setup failing due to NOT_REGISTERED issue

2016-03-15 Thread Digvijay B Ukirde

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 <mihail...@gmail.com>
To: Digvijay B Ukirde/India/IBM@IBMIN
Cc: "openstack-infra@lists.openstack.org"
<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.Independ

Re: [OpenStack-Infra] [Third-party CI] - Running CI setup failing due to NOT_REGISTERED issue

2016-03-15 Thread Mikhail Medvedev
ndentPipelineManager:  types: comment-added comments: (?i)^(Patch Set [0-9]+:)?(
> [\w\\+-]*)*(\n\n)?\s*check(( (?:bug|lp)[\s#:]*(\d+))|( patch))\s*$>
> 2016-03-15 12:14:21,548 INFO zuul.IndependentPipelineManager: Projects:
> 2016-03-15 12:14:21,548 INFO zuul.IndependentPipelineManager: On start:
> 2016-03-15 12:14:21,548 INFO zuul.IndependentPipelineManager: []
> 2016-03-15 12:14:21,548 INFO zuul.IndependentPipelineManager: On success:
> 2016-03-15 12:14:21,548 INFO zuul.IndependentPipelineManager: []
> 2016-03-15 12:14:21,549 INFO zuul.IndependentPipelineManager: On failure:
> 2016-03-15 12:14:21,549 INFO zuul.IndependentPipelineManager: []
> 2016-03-15 12:14:21,549 INFO zuul.IndependentPipelineManager: On
> merge-failure:
> 2016-03-15 12:14:21,549 INFO zuul.IndependentPipelineManager: []
> 2016-03-15 12:14:21,550 INFO zuul.Server: Starting Webapp
> 2016-03-15 12:14:21,552 INFO zuul.Server: Starting RPC
> 2016-03-15 12:14:29,358 INFO zuul.Gerrit: Updating information for 264157,5
> 2016-03-15 12:14:45,383 INFO zuul.Gerrit: Updating information for 292673,2
> 2016-03-15 12:14:46,189 INFO zuul.Gerrit: Updating information for 292213,1
> 2016-03-15 12:14:48,244 INFO zuul.Gerrit: Updating information for 266803,6
> 2016-03-15 12:14:50,327 ERROR zuul.GerritEventConnector: Received
> unrecognized event type 'ref-replicated' from Gerrit. Can not get account
> information.
> 2016-03-15 12:14:50,330 ERROR zuul.GerritEventConnector: Received
> unrecognized event type 'ref-replicated' from Gerrit. Can not get account
> information.
> 2016-03-15 12:14:50,330 ERROR zuul.GerritEventConnector: Received
> unrecognized event type 'ref-replicated' from Gerrit. Can not get account
> information.
> 2016-03-15 12:14:50,330 ERROR zuul.GerritEventConnector: 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:enqueue 0   0   1
> zuul:promote 0   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:merge 0   0   1
> .
>
>
> What is wrong with the configuration?
>
>
>
> Thanks,
> Digivjay
> [image: Inactive hide details for Mikhail Medvedev ---03/14/2016 08:12:59
> PM---Hi Gigvijay, On Mon, Mar 14, 2016 at 7:00 AM, Digvijay B]Mikhail
> Medvedev ---03/14/2016 08:12:59 PM---Hi Gigvijay, On Mon, Mar 14, 2016 at
> 7:00 AM, Digvijay B Ukirde
>
> From: Mikhail Medvedev <mihail...@gmail.com>
> To: Digvijay B Ukirde/India/IBM@IBMIN
> Cc: "openstack-infra@lists.openstack.org" <
> 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
> <digvijay.uki...@in.ibm.com> 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 gett

Re: [OpenStack-Infra] [Third-party CI] - Running CI setup failing due to NOT_REGISTERED issue

2016-03-14 Thread Mikhail Medvedev
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