• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • core
    • None

      Finally tracked down a really perplexing problem I've been having with some windows slaves. It appears that somehow - the slaves are getting "stuck" with a particular set of environment variables. No amount of reconfiguration of the windows box - switching user it runs as, running interactively, etc. would change it.

      The only thing I found that cleared it up is completely deleting the slave from jenkins node list, and re-adding it - then it finally reset what environment variables would be present on the slave. Note - I didn't do ANYTHING other than changing the 'secret' value on the windows box. i.e. I did not reinstall service, relaunch from the nodes list, etc. - just changed the secret that it used to connect with.

      Is this something obvious that I'm missing in how windows slaves are supposed to behave?

      Slave is being launched with java web start.

          [JENKINS-28278] Environment variables "stuck" on windows slave

          Glad to see someone else is seeing it and it's not just my imagination.

          Until I found this it was a complete brain stumper trying to figure out what was going on since the symptom/behavior made no sense whatsoever. I don't know whether it's something with the remote connection or with the environment setting plugin.

          Out of curiosity - do you have the EnvInject plugin installed as well?

          Nathan Neulinger added a comment - Glad to see someone else is seeing it and it's not just my imagination. Until I found this it was a complete brain stumper trying to figure out what was going on since the symptom/behavior made no sense whatsoever. I don't know whether it's something with the remote connection or with the environment setting plugin. Out of curiosity - do you have the EnvInject plugin installed as well?

          I don't have the EnvInject plugin installed.

          I'm similarly glad someone else has this issue as I was also going a little crazy trying to figure out what was going on.

          Brendan Billingsley added a comment - I don't have the EnvInject plugin installed. I'm similarly glad someone else has this issue as I was also going a little crazy trying to figure out what was going on.

          Benjamin Owe added a comment -

          Restarting the master will also do the trick - but a fix is clearly needed.

          Benjamin Owe added a comment - Restarting the master will also do the trick - but a fix is clearly needed.

          I've also run into this. I thought I was going completely crazy. We're using Jenkins ver. 1.611 and Java version 1.7.0_79-b14. We do not have any environment variables set in the config for the master or the slave and the slave is running on Windows. I tried both as a service and from the cmd.exe prompt. We are not using the EnvInject plugin.

          William Woodall added a comment - I've also run into this. I thought I was going completely crazy. We're using Jenkins ver. 1.611 and Java version 1.7.0_79-b14. We do not have any environment variables set in the config for the master or the slave and the slave is running on Windows. I tried both as a service and from the cmd.exe prompt. We are not using the EnvInject plugin.

          Restarting our master fixed this issue for me as well.

          William Woodall added a comment - Restarting our master fixed this issue for me as well.

          Just to be clear though, "restart master =~ clear cache" and not a permanent fix.

          Nathan Neulinger added a comment - Just to be clear though, "restart master =~ clear cache" and not a permanent fix.

          Yeah, I totally agree this is a bug or undocumented behavior or both and something should be done. I should have said restarting our master worked around the issue for us too.

          William Woodall added a comment - Yeah, I totally agree this is a bug or undocumented behavior or both and something should be done. I should have said restarting our master worked around the issue for us too.

          Daniel Beck added a comment -

          Which Jenkins versions are affected by this? Which are the last known good versions?

          Daniel Beck added a comment - Which Jenkins versions are affected by this? Which are the last known good versions?

          Unfortunately, I do not know how long this has been an issue and am not currently in a position to try and roll back for testing.

          I do wonder though - is it only windows, or is it anything launched with JNLP/WebStart/Client initiated? If the latter, it should be significantly easier to test for. All my linux slaves start with SSH, so never really came up there.

          Nathan Neulinger added a comment - Unfortunately, I do not know how long this has been an issue and am not currently in a position to try and roll back for testing. I do wonder though - is it only windows, or is it anything launched with JNLP/WebStart/Client initiated? If the latter, it should be significantly easier to test for. All my linux slaves start with SSH, so never really came up there.

          Daniel Beck added a comment -

          Appears to duplicate JENKINS-27739 for which I've proposed a fix.

          Daniel Beck added a comment - Appears to duplicate JENKINS-27739 for which I've proposed a fix.

            Unassigned Unassigned
            nneul Nathan Neulinger
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: