[JIRA] (JENKINS-57364) jenkins cannot provision new agent with openstack-cloud-plugin

32 views
Skip to first unread message

agatha408.chen@gmail.com (JIRA)

unread,
May 8, 2019, 1:27:02 AM5/8/19
to jenkinsc...@googlegroups.com
agatha chen created an issue
 
Jenkins / Bug JENKINS-57364
jenkins cannot provision new agent with openstack-cloud-plugin
Issue Type: Bug Bug
Assignee: Oliver Gondža
Attachments: openstack-cloud-log.PNG
Components: openstack-cloud-plugin
Created: 2019-05-08 05:26
Environment: jenkins master OS: Red Hat Enterprise Linux Server 7.6 (Maipo)
jenkins master : ver. 2.150.3
openstack-cloud-plugin: 2.45
openstack host: huracan 2.2
Priority: Minor Minor
Reporter: agatha chen

I use openstack cloud plugin to provision agents, several days ago I found that it cannot create new agents. After I click "provision via OpenStack Cloud Plugin " button, it shows "provisioning started" and then nothing happened. the number of agents is not at maximum.  No new instance is created on openstack host. And there are no error message from jenkins log. please check from attachment. 

the openstack host works fine and I can create new instances manually using same template that used in openstack cloud plugin.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

ogondza@gmail.com (JIRA)

unread,
May 10, 2019, 1:32:02 AM5/10/19
to jenkinsc...@googlegroups.com
Oliver Gondža commented on Bug JENKINS-57364
 
Re: jenkins cannot provision new agent with openstack-cloud-plugin

Thanks for the report, though I am afraid the information are incomplete to diagnose the cause.

  • Are the nodes provisioned based on demand in queue (IOW, when you do not provisioned manually)?
  • Can you attach actual log file instead of the UI logger screenshot?

Also, note the "provisioning started" is displayed even when there is a failure (https://github.com/jenkinsci/openstack-cloud-plugin/issues/254).

agatha408.chen@gmail.com (JIRA)

unread,
May 13, 2019, 1:30:02 AM5/13/19
to jenkinsc...@googlegroups.com

Oliver Gondža I'm not sure where should I get the full log of openstack cloud plugin, could you describe the way or the path where log files are stored?

ogondza@gmail.com (JIRA)

unread,
May 13, 2019, 2:56:01 AM5/13/19
to jenkinsc...@googlegroups.com

It depends on the way you deploy Jenkins, consult relevant documentation. For upstream packages it is /var/log/jenkins/jenkins.log.

BTW, have you configured the UI logger according to https://wiki.jenkins.io/display/JENKINS/Openstack+Cloud+Plugin ?

agatha408.chen@gmail.com (JIRA)

unread,
May 13, 2019, 3:06:01 AM5/13/19
to jenkinsc...@googlegroups.com

agatha408.chen@gmail.com (JIRA)

unread,
May 13, 2019, 3:08:02 AM5/13/19
to jenkinsc...@googlegroups.com
agatha chen commented on Bug JENKINS-57364
 
Re: jenkins cannot provision new agent with openstack-cloud-plugin

Oliver Gondža I just upload the jenkins.log.

and yes, I configured the UI logger according to this plugin wiki.

ogondza@gmail.com (JIRA)

unread,
May 13, 2019, 3:54:02 AM5/13/19
to jenkinsc...@googlegroups.com

Hmm, there is nothing OpenStack related. Can you hit the button while capturing the communication (using https://developer.mozilla.org/en-US/docs/Tools/Network_Monitor/request_details for example)? I am interested if there is a AJAX request to /cloud/CLOUD_NAME/provision, and if there is, what is the status and response body.

agatha408.chen@gmail.com (JIRA)

unread,
May 13, 2019, 4:21:02 AM5/13/19
to jenkinsc...@googlegroups.com
agatha chen updated an issue
Change By: agatha chen
Attachment: reposonse-02.PNG
Attachment: response-01.PNG

ogondza@gmail.com (JIRA)

unread,
May 13, 2019, 4:25:02 AM5/13/19
to jenkinsc...@googlegroups.com
 
Re: jenkins cannot provision new agent with openstack-cloud-plugin

Good, no we know it is server rejecting the request for some reason (400 code) and it is https://github.com/jenkinsci/openstack-cloud-plugin/issues/254 that fails to show the cause to you. Please peak in into a response body to see the actual error message from the server side. You might be able to address that even without fixing #254.

agatha408.chen@gmail.com (JIRA)

unread,
May 13, 2019, 4:25:02 AM5/13/19
to jenkinsc...@googlegroups.com

Oliver Gondža hi, I upload the response snapshot when I clicked the provision button, the status shows '400 bad request'.

agatha408.chen@gmail.com (JIRA)

unread,
May 13, 2019, 4:32:03 AM5/13/19
to jenkinsc...@googlegroups.com

ogondza@gmail.com (JIRA)

unread,
May 13, 2019, 4:33:01 AM5/13/19
to jenkinsc...@googlegroups.com
Oliver Gondža commented on Bug JENKINS-57364
 
Re: jenkins cannot provision new agent with openstack-cloud-plugin

Yes, though that does not say more than there is a problem. What the problem is is written in the response body, You have attached headers only. You should see an error message in the response body (in <error> tags).

agatha408.chen@gmail.com (JIRA)

unread,
May 13, 2019, 4:39:02 AM5/13/19
to jenkinsc...@googlegroups.com

from snapshot response-03.png, it seems like the number of instances has reached the max value.  I have set the max number of instances in default slave options, and I have two templates, one is use inherited number and the other use custom set number. I now confuse that which number is working.

agatha408.chen@gmail.com (JIRA)

unread,
May 13, 2019, 5:04:03 AM5/13/19
to jenkinsc...@googlegroups.com

Oliver Gondža hi, now I am sure that it's the max number restriction. But I'm not sure which number is working. Is the number of cloud instances accumulated?

ogondza@gmail.com (JIRA)

unread,
May 13, 2019, 5:10:02 AM5/13/19
to jenkinsc...@googlegroups.com

Yes, the instance cap on template is applied on template level but the one on cloud level is not inherited (like all other values) but applied cumulatively.

agatha408.chen@gmail.com (JIRA)

unread,
May 13, 2019, 5:28:03 AM5/13/19
to jenkinsc...@googlegroups.com

Oliver Gondža Thank you, I will change the number settings of cloud. close the ticket now.

agatha408.chen@gmail.com (JIRA)

unread,
May 13, 2019, 5:29:01 AM5/13/19
to jenkinsc...@googlegroups.com
agatha chen closed an issue as Not A Defect
 

it's related to the max number of instances of the cloud plugin.

Change By: agatha chen
Status: Open Closed
Resolution: Not A Defect
Reply all
Reply to author
Forward
0 new messages