Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-68785

No log messages for inbound agents after the first message (regression in 2.310)

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • 2.357, 2.346.2

      Jenkins 2.343 and later (including 2.346.1) reject connections by unsupported remoting versions.  Connections from an agent using a remoting version older than 3.14 are rejected. 

      Users that want to connect those older agents must set the "escape hatch" system property hudson.slaves.SlaveComputer.allowUnsupportedRemotingVersions=true.
      When the connection is rejected, the implementation provides a message, but when running Jenkins 2.346.1, the message does not appear for inbound agents. It does appear for outbound agents (like ssh).

      I've confirmed that a connection from an unsupported remoting version (3.12 in my case) is correctly rejected when the escape hatch has its default value. I've confirmed that a connection from an unsupported remoting version is accepted when the escape hatch value is set to true. The end result is functioning as expected, though the message to the administrator is missing.

      Steps to duplicate the problem

      1. Download JENKINS-68785.tgz to a Linux computer and unpack it into an empty directory with tar xzvf JENKINS-68785.tgz
      2. Start the controller from one terminal with the command cd JENKINS-68785/ && bash ./README
      3. Open a web browser to the nodes page of that controller with http://localhost:8080/computer/ , confirm that "an-unsupported-agent" is defined and not connected
      4. Start the inbound agent from another terminal with the command cd JENKINS-68785-agent && bash ./README
      5. Open a web browser to the nodes page and confirm that "an-unsupported-agent" is defined, not connected, and displaying the error message "This agent is offline because Jenkins failed to launch the agent process on it."
      6. Click the "log details" link and confirm that the only visible message is the initial connection attempt from the inbound agent

      Expected result

      When an unsupported remoting version connects to the Jenkins controller as an inbound agent, the rejected connection should be logged in a way that is available to the administrator.

      Actual result

      When an unsupported remoting version connects to the Jenkins controller as an inbound agent, the rejected connection is noted on the Jenkins agent web page with the message:

      This agent is offline because Jenkins failed to launch the agent process on it. See log for more details

      The "See log for more details" text is a hyperlink. The log page available through that hyperlink includes the message on my installation:

      Inbound agent connected from testing-a.markwaite.net/172.16.16.113:60880

      It does not include any message explaining why the connection was rejected.

      It would help the administrator understand the problem if an explanatory message were displayed on the agent log page.

          [JENKINS-68785] No log messages for inbound agents after the first message (regression in 2.310)

          Mark Waite created issue -
          Mark Waite made changes -
          Description Original: Jenkins 2.343 and later (including 2.346.1) rejects connections by unsupported remoting versions.  Connections from an agent using a remoting version older than 3.14 are rejected. 

          Users that want to connect those older agents must set the "escape hatch" system property {{hudson.slaves.SlaveComputer.allowUnsupportedRemotingVersions=true  }}.
           When the connection is rejected, the implementation provides a message, but when running Jenkins 2.346.1-rc2, the message does not appear.

          h3. Expected result

          When an unsupported remoting version connects to the Jenkins controller, the rejected connection should be logged in a way that is available to the administrator.

          I've confirmed that a connection from an unsupported remoting version (3.12 in my case) is correctly rejected when the escape hatch has its default value. I've confirmed that a connection from an unsupported remoting version is accepted when the escape hatch value is set to {{{}true{}}}. The end result is functioning as expected, though the message to the administrator is missing.

          h3. Actual result

          When an unsupported remoting version connects to the Jenkins controller, the rejected connection is noted on the Jenkins agent web page with the message:
          {quote}{color:#ff0000}This agent is offline because Jenkins failed to launch the agent process on it.{color} See log for more details
          {quote}
          The "See log for more details" text is a hyperlink. The log page available through that hyperlink includes the message on my installation:
          {quote}Inbound agent connected from testing-a.markwaite.net/172.16.16.113:60880
          {quote}
          It does not include any message explaining why the connection was rejected.

          It would help the administrator understand the problem if an explanatory message were displayed on the agent log page.
          New: Jenkins 2.343 and later (including 2.346.1) rejects connections by unsupported remoting versions.  Connections from an agent using a remoting version older than 3.14 are rejected. 

          Users that want to connect those older agents must set the "escape hatch" system property \{{hudson.slaves.SlaveComputer.allowUnsupportedRemotingVersions=true  }}.
          When the connection is rejected, the implementation provides a message, but when running Jenkins 2.346.1-rc2, the message does not appear.

          I've confirmed that a connection from an unsupported remoting version (3.12 in my case) is correctly rejected when the escape hatch has its default value. I've confirmed that a connection from an unsupported remoting version is accepted when the escape hatch value is set to {{{}true{}}}. The end result is functioning as expected, though the message to the administrator is missing.
          h3. Expected result

          When an unsupported remoting version connects to the Jenkins controller, the rejected connection should be logged in a way that is available to the administrator.
          h3. Actual result

          When an unsupported remoting version connects to the Jenkins controller, the rejected connection is noted on the Jenkins agent web page with the message:
          {quote}{color:#ff0000}This agent is offline because Jenkins failed to launch the agent process on it.{color} See log for more details
          {quote}
          The "See log for more details" text is a hyperlink. The log page available through that hyperlink includes the message on my installation:
          {quote}Inbound agent connected from testing-a.markwaite.net/172.16.16.113:60880
          {quote}
          It does not include any message explaining why the connection was rejected.

          It would help the administrator understand the problem if an explanatory message were displayed on the agent log page.
          Mark Waite made changes -
          Description Original: Jenkins 2.343 and later (including 2.346.1) rejects connections by unsupported remoting versions.  Connections from an agent using a remoting version older than 3.14 are rejected. 

          Users that want to connect those older agents must set the "escape hatch" system property \{{hudson.slaves.SlaveComputer.allowUnsupportedRemotingVersions=true  }}.
          When the connection is rejected, the implementation provides a message, but when running Jenkins 2.346.1-rc2, the message does not appear.

          I've confirmed that a connection from an unsupported remoting version (3.12 in my case) is correctly rejected when the escape hatch has its default value. I've confirmed that a connection from an unsupported remoting version is accepted when the escape hatch value is set to {{{}true{}}}. The end result is functioning as expected, though the message to the administrator is missing.
          h3. Expected result

          When an unsupported remoting version connects to the Jenkins controller, the rejected connection should be logged in a way that is available to the administrator.
          h3. Actual result

          When an unsupported remoting version connects to the Jenkins controller, the rejected connection is noted on the Jenkins agent web page with the message:
          {quote}{color:#ff0000}This agent is offline because Jenkins failed to launch the agent process on it.{color} See log for more details
          {quote}
          The "See log for more details" text is a hyperlink. The log page available through that hyperlink includes the message on my installation:
          {quote}Inbound agent connected from testing-a.markwaite.net/172.16.16.113:60880
          {quote}
          It does not include any message explaining why the connection was rejected.

          It would help the administrator understand the problem if an explanatory message were displayed on the agent log page.
          New: Jenkins 2.343 and later (including 2.346.1) reject connections by unsupported remoting versions.  Connections from an agent using a remoting version older than 3.14 are rejected. 

          Users that want to connect those older agents must set the "escape hatch" system property \{{hudson.slaves.SlaveComputer.allowUnsupportedRemotingVersions=true  }}.
          When the connection is rejected, the implementation provides a message, but when running Jenkins 2.346.1-rc2, the message does not appear.

          I've confirmed that a connection from an unsupported remoting version (3.12 in my case) is correctly rejected when the escape hatch has its default value. I've confirmed that a connection from an unsupported remoting version is accepted when the escape hatch value is set to {{{}true{}}}. The end result is functioning as expected, though the message to the administrator is missing.
          h3. Expected result

          When an unsupported remoting version connects to the Jenkins controller, the rejected connection should be logged in a way that is available to the administrator.
          h3. Actual result

          When an unsupported remoting version connects to the Jenkins controller, the rejected connection is noted on the Jenkins agent web page with the message:
          {quote}{color:#ff0000}This agent is offline because Jenkins failed to launch the agent process on it.{color} See log for more details
          {quote}
          The "See log for more details" text is a hyperlink. The log page available through that hyperlink includes the message on my installation:
          {quote}Inbound agent connected from testing-a.markwaite.net/172.16.16.113:60880
          {quote}
          It does not include any message explaining why the connection was rejected.

          It would help the administrator understand the problem if an explanatory message were displayed on the agent log page.
          Mark Waite made changes -
          Summary Original: Unsupported agent version is disconnected without a log message New: No log message when an unsupported agent version is disconnected
          Basil Crow made changes -
          Attachment New: Screenshot_20220617_214838.png [ 58220 ]
          Basil Crow made changes -
          Assignee New: Basil Crow [ basil ]
          Basil Crow made changes -
          Labels New: regression
          Basil Crow made changes -
          Summary Original: No log message when an unsupported agent version is disconnected New: No log messages for inbound agents after the first message (regression in 2.310)
          Basil Crow made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Basil Crow made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Basil Crow made changes -
          Remote Link New: This issue links to "jenkinsci/jenkins#6672 (Web Link)" [ 27850 ]

            basil Basil Crow
            markewaite Mark Waite
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: