[JIRA] (JENKINS-57713) Cloud agent provisioning errors due to Remoting behaviour change

23 views
Skip to first unread message

jnord@cloudbees.com (JIRA)

unread,
May 28, 2019, 8:38:01 AM5/28/19
to jenkinsc...@googlegroups.com
James Nord updated an issue
 
Jenkins / Bug JENKINS-57713
Cloud agent provisioning errors due to Remoting behaviour change
Change By: James Nord
Summary: Cloud agent provisioning errors due to Remoting changing behaviour change
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

jglick@cloudbees.com (JIRA)

unread,
May 28, 2019, 9:03:03 AM5/28/19
to jenkinsc...@googlegroups.com

jglick@cloudbees.com (JIRA)

unread,
May 28, 2019, 9:03:04 AM5/28/19
to jenkinsc...@googlegroups.com

witokondoria@gmail.com (JIRA)

unread,
May 28, 2019, 5:47:01 PM5/28/19
to jenkinsc...@googlegroups.com
Javier Delgado commented on Bug JENKINS-57713
 
Re: Cloud agent provisioning errors due to Remoting behaviour change

Certainly, trying to connect before the agent creation will cause the remoting attempt to fail and exit. The reconnect flag wont cover the initial bug, as it is interesting to keep on reconnecting while the agent is still registered (but stop doing so if the agent gets removed as happened after a master restart)

Is there some rule or recommendation about the procedure and order of the "agent endpoint register" and "remoting start" order? It seems weird to kick a process that will have to retry until an endpoint becomes available

ogondza@gmail.com (JIRA)

unread,
May 30, 2019, 4:47:01 AM5/30/19
to jenkinsc...@googlegroups.com

The revert of the regression (JENKINS-57759) is landing to next Weekly and 1.176.1

o.v.nenashev@gmail.com (JIRA)

unread,
Jun 11, 2019, 7:21:02 AM6/11/19
to jenkinsc...@googlegroups.com

The weekly revert was done in Jenkins 2.180. 

 

jthompson@cloudbees.com (JIRA)

unread,
Jun 11, 2019, 1:51:02 PM6/11/19
to jenkinsc...@googlegroups.com

It's not clear to me how to preserve the sequencing behavior describes and also achieve the sequencing change Javier Delgado desired in #JENKINS-46515. Different scenarios or implementations rely on or are impacted by the sequence differently. There might be some way to add a flag to invoke the new behavior, while not impacting the existing but I'm not sure if that could meet the needs. Unfortunately, the sequencing isn't well-specified or clarified.

I'll reference this Jira issue to remove the changes for #JENKINS-46515 / jenkinsci/remoting#193 from the Remoting master branch. Once done, I'll release a new Remoting version with the other changes.

ogondza@gmail.com (JIRA)

unread,
Jun 12, 2019, 12:34:03 AM6/12/19
to jenkinsc...@googlegroups.com

Jeff Thompson, I agree a switch to opt-in/out of the behavior is about the only thing to do as far as I can see. I do not think it is sane to rely on any asumptions with regards the sequence of actions on master/agent during cloud provisioning.

jthompson@cloudbees.com (JIRA)

unread,
Jun 12, 2019, 4:52:01 PM6/12/19
to jenkinsc...@googlegroups.com
Jeff Thompson started work on Bug JENKINS-57713
 
Change By: Jeff Thompson
Status: Open In Progress

jthompson@cloudbees.com (JIRA)

unread,
Jun 20, 2019, 3:40:03 PM6/20/19
to jenkinsc...@googlegroups.com
Jeff Thompson updated Bug JENKINS-57713
 

Removed the problematic change from Remoting in version 3.31.

Change By: Jeff Thompson
Status: In Progress Fixed but Unreleased
Resolution: Fixed
Released As: Remoting 3.33

dbeck@cloudbees.com (JIRA)

unread,
Jun 24, 2019, 7:25:03 AM6/24/19
to jenkinsc...@googlegroups.com
Change By: Daniel Beck
Status: Fixed but Unreleased Resolved
Released As: Remoting 3.33 , jenkins-2.182
Reply all
Reply to author
Forward
0 new messages