Hi Jeremy. Thanks for your help! I've fixed the configuration.
Thanks & Best Regards, Godwin Hu(胡国清) Software Engineer IBM China System and Technology Lab(CSTL), Beijing Tel(Seat): 86-010-82451453 Location : Ring Building, 1BW270 E-mail Address: [email protected] Address: IBM ZGC Campus. Ring Building, 28# ZhongGuanCun Software Park, Shang Di, Beijing P.R.China 100193 From: Jeremy Stanley <[email protected]> To: Guo Qing GH Hu/China/IBM@IBMCN, Cc: [email protected], Li Jun Jiang/China/IBM@IBMCN, Shao Mei SM Ji/China/IBM@IBMCN Date: 02/13/2014 02:28 PM Subject: Re: [OpenStack-Infra] Jenkins job may run on same node in CI environment. On 2014-02-11 16:47:26 +0800 (+0800), Guo Qing GH Hu wrote: > I found that in following scenario jenkins job may run on same > node in CI environment. > > [cid] > When nodepool is trying to delete the node 1 on jenkins, but the > node has been assigned to queued 2, so nodepool will be failed to > delete node 1. [...] I suspect your Zuul layout may not be configured to pass the OFFLINE_NODE_WHEN_COMPLETE parameter with that job, which should cause the Jenkins Gearman plugin to atomically offline a node at job completion without giving Jenkins an opportunity to assign it another job. For OpenStack Infra we do this with a single_use_node parameter function in the modules/openstack_project/files/zuul/openstack_functions.py file in openstack-infra/config. -- Jeremy Stanley
_______________________________________________ OpenStack-Infra mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
