[JIRA] (JENKINS-58352) Issues related to the EC2 plugins

[karthickthanigaimani@nbnco.com.au (JIRA)]

karthick thanigaimani created an issue

Jenkins / JENKINS-58352 Issues related to the EC2 plugins Issue Type: Bug Assignee: Unassigned Components: jenkins-tag-cloud Created: 2019-07-05 01:49 Environment: PROD Priority: Major Reporter: karthick thanigaimani Jenkins Version - 2.114Jenkins Version - 2.114 amazon EC2 plugin version -  1.39 and also tried with 1.44.1Amazon web services SDK -  1.11.264 and also tried with 1.11.562 We have slave nodes (reserved instances) with node labels as "Deploy-Slave" or "Build-Slave" and when we try to spin up or launch them manaually via jenkins we are gettign this error. java.lang.IllegalArgumentException: hostname cannot be null at com.amazonaws.util.AwsHostNameUtils.parseRegion(AwsHostNameUtils.java:79) at com.amazonaws.util.AwsHostNameUtils.parseRegionName(AwsHostNameUtils.java:59) at com.amazonaws.AmazonWebServiceClient.computeSignerByURI(AmazonWebServiceClient.java:332) at com.amazonaws.AmazonWebServiceClient.setEndpoint(AmazonWebServiceClient.java:228) at hudson.plugins.ec2.EC2Cloud.connect(EC2Cloud.java:671) at hudson.plugins.ec2.EC2Cloud.connect(EC2Cloud.java:639) at hudson.plugins.ec2.EC2Cloud.countCurrentEC2Slaves(EC2Cloud.java:363) at hudson.plugins.ec2.EC2Cloud.getPossibleNewSlavesCount(EC2Cloud.java:502) at hudson.plugins.ec2.EC2Cloud.getNewOrExistingAvailableSlave(EC2Cloud.java:522) at hudson.plugins.ec2.EC2Cloud.doProvision(EC2Cloud.java:340) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(St Also, any jenkins job configured use these nodes are giving the below error and just hanging: Still waiting to schedule taskAll nodes of label 'Build-Slave' are offline we tried changing the instance type for the nodes, verified AMI and able to launch a seperate eC2 but of no help. We also modified the instance cap settings as well as number of executors which did not help either. Could you please check if there is any bug or known issue that is causing this behaviour. Thank you. Regards,Karthick Add Comment

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

[karthickthanigaimani@nbnco.com.au (JIRA)]

karthick thanigaimani commented on JENKINS-58352

Re: Issues related to the EC2 plugins any pointers please?

Add Comment

[parkinson.jeremy@gmail.com (JIRA)]

Jeremy Parkinson commented on JENKINS-58352

Re: Issues related to the EC2 plugins

We are having this issue as well and it is a priority one for us. Everything was working fine until yesterday.

Add Comment

[parkinson.jeremy@gmail.com (JIRA)]

Jeremy Parkinson updated an issue

Jenkins / JENKINS-58352

Issues related to the EC2 plugins

Change By: Jeremy Parkinson Priority: Major Blocker

Add Comment

[jocgjr@yahoo.com (JIRA)]

Oscar Garcia commented on JENKINS-58352

Re: Issues related to the EC2 plugins same error, do we have updates on this?

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[pskillen@gmail.com (JIRA)]

Patrick Skillen commented on JENKINS-58352

Re: Issues related to the EC2 plugins

I was able to work around the issue, though I'm not entirely sure what specifically fixed it. Things to try: Ensure Jenkins Master has outbound Internet access Ensure Master has IAM permission "ec2:Describe*" on us-east-1 (or maybe us-west-1, whichever is the default) This was needed to load the list of available regions Once you've selected a region, everything should work

Add Comment