|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
I've started to observe this issue after migrating Jenkins to Amazon VPC (instead of EC2-Classic). All our builds and tests happen on EC2 instances launched from the same set of AMIs. This particular failure is happening with a node running Ubuntu 12.04. Master has Ubuntu 14.04 and Jenkins 1.571. The problem seems strangely intermittent, but once it occurs I need to destroy the offending machine and launch a new one for the build to work again.