![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Francis Upton
|
|
Components:
|
ec2 |
|
Created:
|
23/Jul/14 7:15 AM
|
|
Description:
|
When the set of labels is changed for a configured slave in the EC2 plugin's global config (under "Configure Jenkins"), it forgets about existing nodes and launches new ones.
It should instead relabel existing nodes with the new labels on first launch. Or at least terminate the old nodes. As it is, you land up with a bunch of duplicate nodes.
Observed with idle timeout enabled, and stop on idle enabled, with nodes idled down at the time of configuration change.
|
|
Environment:
|
EC2-plugin 1.23
|
|
Project:
|
Jenkins
|
|
Labels:
|
slave
labels
ec2
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Craig Ringer
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
