[JIRA] (JENKINS-62037) EC2 Node with job lost during master restart with maxTotalUses

37 views
Skip to first unread message

nigel.armstrong@braincorp.com (JIRA)

unread,
Apr 23, 2020, 9:13:02 PM4/23/20
to jenkinsc...@googlegroups.com
Nigel Armstrong created an issue
 
Jenkins / Bug JENKINS-62037
EC2 Node with job lost during master restart with maxTotalUses
Issue Type: Bug Bug
Assignee: FABRIZIO MANFREDI
Components: ec2-plugin
Created: 2020-04-24 01:12
Environment: EC2-Plugin: 1.49.1
Priority: Major Major
Reporter: Nigel Armstrong

I have a build running on an ec2 slave (with maxTotalUses set to 1). 

Then jenkins master is restarted. 

When the jenkins master comes back up it reconnects the node then disposes of them because EC2RetentionStrategy#taskAccepted: maxTotalUses drained - suspending agent i-xxxx, but it should not because these nodes are still in use with the previous build.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

nigel.armstrong@braincorp.com (JIRA)

unread,
Apr 24, 2020, 2:19:02 PM4/24/20
to jenkinsc...@googlegroups.com
Nigel Armstrong commented on Bug JENKINS-62037
 
Re: EC2 Node with job lost during master restart with maxTotalUses

After testing this a bit more, It seems to be a race condition, because I can't get it to happen consistently. 

Reply all
Reply to author
Forward
0 new messages