-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
I've noticed cases where I manually change the label on a node provisioned by ec2-plugin, run a build on it associated with the new label, but after the build, the node's configuration has reverted to the original label. That can then trigger JENKINS-34412, preventing launch of any new nodes.
For example, I provisioned a node i-599b2fec with an AMI associated with the "linux_test" label. After some verification builds, I changed the AMI to the "linux" label, and configured i-599b2fec to have the "linux" label instead of "linux_test". I triggered a build restricted to the "linux" label, which ran on i-599b2fec. On completion of the build, i-599b2fec was configured to have the "linux_test" label again.