[JIRA] (JENKINS-61788) jclouds single-use slave never cleaned up
Title: Message Title Fritz Elfert updated JENKINS-61788 As I got no further feedback, I now released v1.18 and close this issue. Feel free to reopen this issue, if you are not satisfied with the solution. Note: A slight delay (~ 1min) is still happening between marking a slave offline and actually deleting the instance in the cloud. This works as designed. Jenkins / JENKINS-61788 jclouds single-use slave never cleaned up Change By: Fritz Elfert Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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]. To view this discus
[JIRA] (JENKINS-61788) jclouds single-use slave never cleaned up
Title: Message Title Major Hayden commented on JENKINS-61788 Re: jclouds single-use slave never cleaned up Thanks for the quick fix. I'll try to get a look at this as soon as I can. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205628.1585853221000.9684.1586782740391%40Atlassian.JIRA.
[JIRA] (JENKINS-61788) jclouds single-use slave never cleaned up
Title: Message Title Fritz Elfert updated JENKINS-61788 Jenkins / JENKINS-61788 jclouds single-use slave never cleaned up Change By: Fritz Elfert Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205628.1585853221000.9367.1586616120236%40Atlassian.JIRA.
[JIRA] (JENKINS-61788) jclouds single-use slave never cleaned up
Title: Message Title Fritz Elfert edited a comment on JENKINS-61788 Re: jclouds single-use slave never cleaned up Please try [this build|https://ci.jenkins.io/job/Plugins/job/jclouds-plugin/job/master/68/artifact/jclouds-plugin/target/jclouds-jenkins.hpi]. If this fixes the problem for you, I will crate create a new release. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205628.1585853221000.9365.1586616060210%40Atlassian.JIRA.
[JIRA] (JENKINS-61788) jclouds single-use slave never cleaned up
Title: Message Title Fritz Elfert commented on JENKINS-61788 Re: jclouds single-use slave never cleaned up Please try this build. If this fixes the problem for you, I will crate a new release. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205628.1585853221000.9363.1586616060173%40Atlassian.JIRA.
[JIRA] (JENKINS-61788) jclouds single-use slave never cleaned up
Title: Message Title Fritz Elfert started work on JENKINS-61788 Change By: Fritz Elfert Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205628.1585853221000.9361.1586614560323%40Atlassian.JIRA.
[JIRA] (JENKINS-61788) jclouds single-use slave never cleaned up
Title: Message Title Fritz Elfert commented on JENKINS-61788 Re: jclouds single-use slave never cleaned up Well this turned out to be a bug. The retention time for the single-use slaves was never reset to zero. Therefore, the normal RetentionStrategy handler never touched them. Will fix this asap. -Fritz Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205628.1585853221000.9359.1586614560297%40Atlassian.JIRA.
[JIRA] (JENKINS-61788) jclouds single-use slave never cleaned up
Title: Message Title Major Hayden created an issue Jenkins / JENKINS-61788 jclouds single-use slave never cleaned up Issue Type: Improvement Assignee: Fritz Elfert Components: jclouds-plugin Created: 2020-04-02 18:47 Environment: Jenkins 2.229 jclouds plugin 2.17 Priority: Minor Reporter: Major Hayden When I use the jclouds plugin to spawn instances at DigitalOcean and EC2, I noticed that the single-use slaves are never removed. They are marked offline as soon as the job finishes, but they remain offline in Jenkins and they are active with the cloud provider. As soon as the job finishes, I see this in the logs: 2020-04-02 18:30:42.634+ [id=3070] WARNING j.p.j.c.JCloudsOneOffSlave$JCloudsOneOffSlaveDisposer#tearDown: Taking single-use slave [COMPUTER_NAME] offline. I let it sit for two hours and nothing changed. I had to delete the agent manually from inside Jenkins' build executors listing. Am I missing a step? I'll gladly turn on more debug logging if that would help diagnose the issue.
