[JIRA] (JENKINS-53879) EC2 workers terminated before connection can be established, only on v1.40
Title: Message Title Stephen Rosen closed an issue as Duplicate Jenkins / JENKINS-53879 EC2 workers terminated before connection can be established, only on v1.40 Change By: Stephen Rosen Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
[JIRA] (JENKINS-53879) EC2 workers terminated before connection can be established, only on v1.40
Title: Message Title Stephen Rosen commented on JENKINS-53879 Re: EC2 workers terminated before connection can be established, only on v1.40 It very well could be a duplicate; apologies if so. I didn't find that issue when looking at open issues, probably because I was looking for things about "premature termination" not "failure to connect". Let's mark it as a dup and close, and if I find it persists after that bug is fixed, I'll reopen. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
[JIRA] (JENKINS-53879) EC2 workers terminated before connection can be established, only on v1.40
Title: Message Title Stephen Rosen created an issue Jenkins / JENKINS-53879 EC2 workers terminated before connection can be established, only on v1.40 Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2018-10-02 19:34 Environment: Jenkins ver. 2.138.1 Ubuntu 14.04 Priority: Major Reporter: Stephen Rosen I just did my monthly round of plugin upgrades and found that EC2 workers were failing to connect. Downgrading this plugin, and only this plugin, to v1.39 resolved the issue, so I'm fairly confident this is the source of the behavior. When I watched the activity, I see worker nodes spinning up, correctly, based on our various labels and job requirements. They get to the running state in EC2, but shortly thereafter (< 1 minute) they are terminated. I believe that this is happening during the guest OS boot time, as I tried polling for connections on port 22 from the master node and never got a success – and our workers are all configured to run sshd open to the master on 22. All of our nodes are configured with Launch Timeout in Seconds = 300, but this failure was very consistent and the last time I measured our launch times, they were around 3.5 minutes. If I had to venture a guess, I would say that something has changed in terms of the leniency with which nodes are treated as they start, and their boot times are being counted differently. If someone can confirm that that's what changed, I'll probably just up my timeouts to 10 minutes and walk away, but I'm not confident that would work.
[JIRA] [github-oauth] (JENKINS-23324) GitHub OAuth 0.17 requires private access to all repositories
Stephen Rosen commented on JENKINS-23324 GitHub OAuth 0.17 requires private access to all repositories We're still running 0.14 until this is fixed. I tried rolling back to 0.16 after updating to 0.19 and it did not fix the problem. Can we please see this as a priority item for 0.20 ? Until a fix for this is in place, no other improvements to the plugin are meaningful. Anyone who doesn't want this kind of access (which is everyone, btw) and cares (should be everyone, but isn't) is forced to use old versions. More complex access control would be great, sure, but not making Jenkins into a giant security hole is a much higher priority. 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.
[JIRA] [throttle-concurrents] (JENKINS-19986) Throttle Concurrent Builds plugin doesn't appear to work
Stpehen Rosen commented on JENKINS-19986 Throttle Concurrent Builds plugin doesnt appear to work We've tried configuring throttle concurrents on multiple builds ranging from 1.536 to 1.542, and it has never worked. I'm fairly sure we're experiencing this same error. I haven't carefully tracked all of the versions and attempted configurations, but we're running Ubuntu 12.04.3 servers on AWS with Jenkins as the only application that these servers are dedicated to. The jobs are free style jobs that pull in git repos and do a simple 'make clean make test' shell action. Primarily, I've been trying to use the same configuration as the OP. This bug desperately needs resolution we get spurious failures on a regular basis without throttle-concurrents. 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/groups/opt_out.
[JIRA] [throttle-concurrents] (JENKINS-19986) Throttle Concurrent Builds plugin doesn't appear to work
Stpehen Rosen commented on JENKINS-19986 Throttle Concurrent Builds plugin doesnt appear to work If you use AWS, launch with ami-bd6d40d4 in us-east and install Jenkins 1.537 and Throttle Concurrents with its dependencies. Otherwise, any server running Ubuntu 12.04 will probably do. Create a category with Maximum Total Concurrents = 1 and Maximum Concurrents Per Node = 1. Put two free style software jobs in this category, with run steps like "sleep 1", and start them both. The erroneous behavior should present itself immediately. 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/groups/opt_out.
[JIRA] [throttle-concurrents] (JENKINS-19986) Throttle Concurrent Builds plugin doesn't appear to work
Stpehen Rosen commented on JENKINS-19986 Throttle Concurrent Builds plugin doesnt appear to work Odd. I can confirm that I am no longer able to produce this error using the same versions and builds that experienced it before. My prior note has a typo, rather than "Maximum Total Concurrents = 1" we want "Maximum Total Concurrents = 0". However, I at least can no longer reproduce. 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/groups/opt_out.
