Open Stack

Hi Zaro,

On 07/24/2015 11:44 PM, Zaro wrote:
> Tang, Have you tried to look at the function registrations and gearman 
> queue on the gearman server as i suggested?  The instructions are in 
> the wiki i referenced (in 'Starting the gearman workers' section).  
> What you are seeing from the gear_client could also be from passing in 
> a function name that does not exist.  Unfortunately the simple 
> gear_client does not check whether the passed in functions are valid 
> so what you want to do is verify that the gearman functions have been 
> registered by using the 'workers' command.
>

Thank you for your suggestion. I have not seen the inside of Gearman.

But I set up a slave node, and the job can run on the slave node.

This is also acceptable for me. So I think I have to go on with my work 
first.
And I'll check what you said later.

Thanks very much. :)

>
> On Fri, Jul 24, 2015 at 1:09 AM, Tang Chen <tangchen at cn.fujitsu.com 
> <mailto:tangchen at cn.fujitsu.com>> wrote:
>
>
>     On 07/24/2015 03:36 PM, Tang Chen wrote:
>>     Hi Zaro,
>>
>>     Thanks to reply.
>>
>>     On 07/24/2015 03:06 PM, Zaro wrote:
>>>     That is correctly, the Jenkins UI will not show any info about
>>>     the gearman queue.  If job is pending in Jenkins that means it's
>>>     been added to the gearman queue and has been moved to the
>>>     jenkins build queue.  The jenkins UI will only show the job once
>>>     it's in the jenkins queue.
>>>
>>>     Hmm.  What happens when you manually start a build by click on
>>>     the build icon in the jenkins UI?
>
>     If I click the build icon in the jenkins UI, the job can run.
>     Wired, isn't it ?
>
>     Thanks.
>
>
>>>     I'm wondering if maybe your labels are configured correctly for
>>>     your jobs and slaves.  Are there any labels on the job or the
>>>     nodes (master or slaves)? I think the jobs would be in a pending
>>>     state if there are labels on nodes and jobs but they do not
>>>     match.  I would check to see if there are any labels on the jobs
>>>     and if there are then I would remove all of the labels and try
>>>     again. There are step by step directions on how to setup the
>>>     gearman-plugin in the jenkins wiki[1] which also shows you how
>>>     to debug by viewing the gearman server queue and function
>>>     registrations.  Try to make sure the functions are registered
>>>     correctly and that the job is in the queue after you run the
>>>     gear-client command.
>>>
>>>     A couple of questions:
>>>     What version of Jenkins are you running? I think openstack runs
>>>     on 1.565.3
>>>     Also I don't think we've ever tested Jenkins and the gearman
>>>     server running on the same machine or VM.  Maybe one thing you
>>>     can try is to run them on separate VMs?
>>
>>     I don't have any label, and only a master, no slave.
>>
>>     My jenkins is 1.609.1.
>>
>>     The whole problem is described here:
>>
>>     http://paste.openstack.org/show/405051/
>>
>>     Please help to check and see.
>>
>>
>>     BTW, I post the problem to #openstack-infra IRC channel. You can
>>     join into that meeting if you'd like to.
>>
>>
>>     Thanks.
>>
>>>
>>>     [1] https://wiki.jenkins-ci.org/display/JENKINS/Gearman+Plugin
>>>
>>>
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150728/e89b14ea/attachment.html>