Upgrade Jenkins EC2 Plugin to 1.18

Bug #1170682 reported by Paul Sokolovsky
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Android Infrastructure
Fix Released
Critical
Paul Sokolovsky

Bug Description

Fathi Boudra wrote:

> https://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin
>
> Version 1.18 (April 9, 2013)
>
> * Add m3.xlarge and m3.2xlarge instance types
> * Failure starting slave nodes (issue #15319)
> * Tags feature is broken (issue #15239)
> * EC2 Nodes which share an AMI ID get the wrong labels (issue #7690)
> * Sometimes starts the wrong instance (issue #15158)
> * Stopped (as opposed to terminated) slaves are counted against the
> active instance count for the purpose of launching; can prevent
> launching of instances (issue #7883)
> * Upgrade aws-java-sdk dependency to 1.3.30
> * Explicitly add MIT license to all plugin code
> * Fallback a manual or timeout-based terminate to stop if terminate
> fails (to avoid charges)
> * Give Jenkins nodes useful names (issue #15078)
> * Keep track of instances being provisioned; use this count when
> determining total/AMI instance caps (issue #6691)
> * Bring back remoteFS in the slave configuration page
> * Let user configure node.mode for EC2 slaves

Revision history for this message
Paul Sokolovsky (pfalcon) wrote :

This should address lp:1068586, lp:1163979, hence critical. Agreed to be deployed after 13.04 release out.

Changed in linaro-android-infrastructure:
status: New → Confirmed
importance: Undecided → Critical
milestone: none → 2013.04
assignee: nobody → Paul Sokolovsky (pfalcon)
Revision history for this message
Paul Sokolovsky (pfalcon) wrote :

Upgrade was performed today. No issues with post-upgrade test builds.

Changed in linaro-android-infrastructure:
status: Confirmed → Fix Committed
Fathi Boudra (fboudra)
Changed in linaro-android-infrastructure:
status: Fix Committed → Fix Released
Revision history for this message
Paul Sokolovsky (pfalcon) wrote :

Upgrade didn't resolve zombie problem:

  Back to List
 Status
 Delete Slave
 Configure
 Build History
 Load Statistics
 Script Console
 Log
 System Information
Build Executor Status
#
Status

ERROR: The instance ID 'i-e4e6e288' does not exist
Status Code: 400, AWS Service: AmazonEC2, AWS Request ID: e6cf45bd-2e9b-47b3-bcfa-890ab58a1d7e, AWS Error Code: InvalidInstanceID.NotFound, AWS Error Message: The instance ID 'i-e4e6e288' does not exist
 at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:614)
 at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:312)
 at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:165)
 at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:6047)
 at com.amazonaws.services.ec2.AmazonEC2Client.describeInstances(AmazonEC2Client.java:2740)
 at hudson.plugins.ec2.EC2Computer._describeInstanceOnce(EC2Computer.java:142)
 at hudson.plugins.ec2.EC2Computer._describeInstance(EC2Computer.java:136)
 at hudson.plugins.ec2.EC2Computer.getState(EC2Computer.java:101)
 at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:56)
 at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:224)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:636)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.