Open Stack

Could you check if you have /var/run/zuul/zuul.pid  ?


-----Original Message-----
From: Hejral, VaclavX [mailto:vaclavx.hejral at intel.com] 
Sent: Tuesday, April 19, 2016 1:34 PM
To: openstack-infra at lists.openstack.org
Cc: Znoinski, Waldemar <waldemar.znoinski at intel.com>; Zetik, RadekX <radekx.zetik at intel.com>
Subject: [OpenStack-Infra] ZUUL does not trigger jobs

Hello, 

zuul 2.1.1.dev131 is not triggering any jobs in jenkins, there is a zuul queue still being added, but it is not triggering jobs.

Nodepool works fine, I have slaves attached to Jenkins, when I remove slave via nodepool delete, new one is created via nodepool and attached to Jenkins.

status and workers  commands show gearman communication is ready ...
build:noop-check-communication:dpc-test-nfv2    0       0       1
...
17 127.0.0.1 dpc-test-nfv2-local_01-213905_exec-0 : build:3rdparty-networking-ci:dpc-test-nfv2 build:zuul-test-02 build:networking-ovs-dpdk-unit_tests:dpc-test-nfv2 build:noop-check-communication:dpc-test-nfv2 build:intel-nfv-tests-ci build:3rdparty-networking-vif-ci:dpc-test-nfv2 build:zuul-test-01:dpc-test-nfv2 build:zuul-test-01 build:networking-ovs-dpdk-unit_tests build:zuul-test-02:dpc-test-nfv2 build:3rdparty-networking-ci build:noop-check-communication build:3rdparty-networking-vif-ci build:intel-nfv-tests-ci:dpc-test-nfv2
...

This job can be triggered manually when I click in Jenkins without issues. But not from zuul.

Building via gearman client is fine as well.
>>
python ./gear_client.py --function=build:noop-check-communication

Tue Apr 19 11:31:08 2016
Sending job: build:noop-check-communication to localhost with params={'OFFLINE_NODE_WHEN_COMPLETE': 'false', 'uuid': '4a1e743d185d472b863123aaa5dd456e'}

Waiting for jobs to finish...

-----  Job Results (Tue Apr 19 11:31:10 2016)  ------

4a1e743d185d472b863123aaa5dd456e : ['{"manager":"sie-lab-214-103.ir.intel.com","node_labels":["master"],"name":"noop-check-communication","worker":"dpc-test-nfv2-local_01-213905_exec-0","number":258,"node_name":"","url":"http://10.237.214.103:8080/job/noop-check-communication/258/"}', '{"result":"SUCCESS","manager":"sie-lab-214-103.ir.intel.com","node_labels":["dpc-test-nfv2","dpc-test-nfv2-local_01-213905"],"name":"noop-check-communication","worker":"dpc-test-nfv2-local_01-213905_exec-0","number":258,"node_name":"dpc-test-nfv2-local_01-213905","url":"http://10.237.214.103:8080/job/noop-check-communication/258/"}']
>>

/var/log/zuul/debug.log shows usual logs + "already ahead" logs as below I presume this is ok

2016-04-19 10:47:13,801 DEBUG zuul.IndependentPipelineManager: Checking for changes needed by <Change 0x7f14caa18c10 304511,16>:
2016-04-19 10:47:13,801 DEBUG zuul.IndependentPipelineManager:   Change <Change 0x7f14caa18c10 304511,16> needs change <Change 0x7f14caac4a50 304510,16>:
2016-04-19 10:47:13,801 DEBUG zuul.IndependentPipelineManager:   Needed change is already ahead in the queue

There are no errors in debug logs in zuul / merger / nodepool which will point to fact what is happening.

ZUUL queue shows a.g. trigger from openstack-dev/ci-sandbox which should trigger just noop-check-communication job.
I tried to uncheck gearman in Jenkins settings, stop Jenkins service, then start it again and check gearman again. Also test connection works. But no change, zuul still does not trigger jobs.
I updated gearman plugin from version 0.1.3 to 0.2.0 and restarted Jenkins (Jenkins ver. 1.642.4) , no change.

I presumed that when I stop zuul service which cleans up the queue, and start zuul again, issue will be gone.
I did exactly that.
Still, zuul does not trigger anything.

Are there any hints how to proceed?

Thank you,
Vaclav

 
--------------------------------------------------------------
Intel Research and Development Ireland Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.


_______________________________________________
OpenStack-Infra mailing list
OpenStack-Infra at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra