following the provisioning of a Jenkins ec2 instance using the ec2 plugin, we have a Chef cookbook modify the ec2 name tag on that instance so, that it is unique per instance in aws. However, doing this breaks that ability for Jenkins builds to detect this already provisioned instance assigned to its label. When I trigger a build using the label of the already provisioned instance, it spawns a brand new instance instead of using the existing one. I don't see this issue when I change the AWS Name Tag for that instance back to what it's set in the global configuration.