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

When a slave is waiting for master to be ready ("Master isnt ready to talk to us on {0}. Will retry again"), the port is not filled in

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Trivial Trivial
    • core, remoting
    • Windows slave; JNLP2, Jenkins 2.31

      Very trivial, but on the slave, the command prompt window doesn't appear to fill out the port correctly anymore (the '{0}' placeholder isn't filled in):

      Nov 16, 2016 10:06:17 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Terminated
Nov 16, 2016 10:06:27 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver waitForReady
INFO: Master isnt ready to talk to us on {0}. Will retry again: response code={1}
Nov 16, 2016 10:06:38 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver waitForReady
INFO: Master isnt ready to talk to us on {0}. Will retry again: response code={1}
Nov 16, 2016 10:06:48 AM hudson.remoting.jnlp.Main$CuiListener status
...

          [JENKINS-39782] When a slave is waiting for master to be ready ("Master isnt ready to talk to us on {0}. Will retry again"), the port is not filled in

          Jeremy Hill created issue -
          Jeremy Hill made changes -
          Summary Original: When a slave is waiting for master to be ready (" Master isnt ready to talk to us on {0}. Will retry again") , the port does not fill in New: When a slave is waiting for master to be ready ("Master isnt ready to talk to us on {0}. Will retry again"), the port is not filled in
          Jeremy Hill made changes -
          Description Original: Very trivial, but on the slave, the command prompt window doesn't appear to fill out the port correctly anymore:

          {code}
          Nov 16, 2016 10:06:17 AM hudson.remoting.jnlp.Main$CuiListener status
          INFO: Terminated
          Nov 16, 2016 10:06:27 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver waitForReady
          INFO: Master isnt ready to talk to us on {0}. Will retry again: response code={1}
          Nov 16, 2016 10:06:38 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver waitForReady
          INFO: Master isnt ready to talk to us on {0}. Will retry again: response code={1}
          Nov 16, 2016 10:06:48 AM hudson.remoting.jnlp.Main$CuiListener status
          ...
          {code}
          		 New: Very trivial, but on the slave, the command prompt window doesn't appear to fill out the port correctly anymore (the '{0}' placeholder isn't filled in):

          {code}
          Nov 16, 2016 10:06:17 AM hudson.remoting.jnlp.Main$CuiListener status
          INFO: Terminated
          Nov 16, 2016 10:06:27 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver waitForReady
          INFO: Master isnt ready to talk to us on {0}. Will retry again: response code={1}
          Nov 16, 2016 10:06:38 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver waitForReady
          INFO: Master isnt ready to talk to us on {0}. Will retry again: response code={1}
          Nov 16, 2016 10:06:48 AM hudson.remoting.jnlp.Main$CuiListener status
          ...
          {code}
          Jeremy Hill made changes -
          Description Original: Very trivial, but on the slave, the command prompt window doesn't appear to fill out the port correctly anymore (the '{0}' placeholder isn't filled in):

          {code}
          Nov 16, 2016 10:06:17 AM hudson.remoting.jnlp.Main$CuiListener status
          INFO: Terminated
          Nov 16, 2016 10:06:27 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver waitForReady
          INFO: Master isnt ready to talk to us on {0}. Will retry again: response code={1}
          Nov 16, 2016 10:06:38 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver waitForReady
          INFO: Master isnt ready to talk to us on {0}. Will retry again: response code={1}
          Nov 16, 2016 10:06:48 AM hudson.remoting.jnlp.Main$CuiListener status
          ...
          {code}
          		 New: Very trivial, but on the slave, the command prompt window doesn't appear to fill out the port correctly anymore (the '\{0\}' placeholder isn't filled in):

          {code}
          Nov 16, 2016 10:06:17 AM hudson.remoting.jnlp.Main$CuiListener status
          INFO: Terminated
          Nov 16, 2016 10:06:27 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver waitForReady
          INFO: Master isnt ready to talk to us on {0}. Will retry again: response code={1}
          Nov 16, 2016 10:06:38 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver waitForReady
          INFO: Master isnt ready to talk to us on {0}. Will retry again: response code={1}
          Nov 16, 2016 10:06:48 AM hudson.remoting.jnlp.Main$CuiListener status
          ...
          {code}
          R. Tyler Croy made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: core [ 21134 ]
          Key Original: INFRA-979 New: JENKINS-39782
          Workflow Original: classic default workflow [ 213574 ] New: JNJira + In-Review [ 213576 ]
          Project Original: Infrastructure [ 10301 ] New: Jenkins [ 10172 ]
          R. Tyler Croy made changes -
          Assignee Original: R. Tyler Croy [ rtyler ]
          Oleg Nenashev made changes -
          Assignee New: Oleg Nenashev [ oleg_nenashev ]
          Oleg Nenashev made changes -
          Component/s New: remoting [ 15489 ]
          Oleg Nenashev made changes -
          Labels New: newbie-friendly

          Oleg Nenashev added a comment -

          vlatombe fixed it in JENKINS-47132

           

          Oleg Nenashev added a comment - vlatombe fixed it in JENKINS-47132  

            oleg_nenashev Oleg Nenashev
            jeremy_hill Jeremy Hill
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: