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

VM abruptly gets restarted through Jenkins.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • vmware-plugin, vsphere-cloud-plugin
    • Jenkins 1.580.2 , Tomcat7 , JRE 7 , Windows 2008 R2 , Vsphere Plugin 1.1.12

      Hello Team,
      We have connected Slave windows 2008 R2 machine to jenkins using vmrun command.

      "C:\Program Files (x86)\VMware\VMware VIX\vmrun.exe" -T server -h <Vcenter_IP> -u <domain\username> -p <password>
      -gu administrator -gp password runProgramInGuest "[DATASTORE] build_vm/build_vm.vmx" -noWait "C:\Program Files (x86)\Java\jre7\bin\java.exe" -jar C:\jenkins\slave.jar -jnlpUrl "http://<JENKINS_IP>/jenkins/computer/BUild_VM/slave-agent.jnlp"

      We observed that build VM gets restarted randomly eventhough the build job is running on that VM. Please check the attachment for details.

        1. Jenkins_VM.jpg
          Jenkins_VM.jpg
          198 kB

          [JENKINS-26543] VM abruptly gets restarted through Jenkins.

          manohar joshi created issue -
          Stephen Connolly made changes -
          Assignee Original: Stephen Connolly [ stephenconnolly ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 160614 ] New: JNJira + In-Review [ 180423 ]

          pjdarton added a comment -

          That looks like you've got the slave node entry in Jenkins configured to be a vSphere node which should be turned on and off on demand - If you're managing the node manually using vmrun etc, you should also manage its power status manually and not tell Jenkins to do it (just tell Jenkins it's a non-vsphere node).

          Alternatively, have Jenkins spin it up on demand and have it automatically connect to Jenkins (e.g. using a scheduled task that runs when the slave boots up) so that it's ok for Jenkins to start/stop it.

          ...or use the cloud functionality to start up as many of these as you like.

          pjdarton added a comment - That looks like you've got the slave node entry in Jenkins configured to be a vSphere node which should be turned on and off on demand - If you're managing the node manually using vmrun etc, you should also manage its power status manually and not tell Jenkins to do it (just tell Jenkins it's a non-vsphere node). Alternatively, have Jenkins spin it up on demand and have it automatically connect to Jenkins (e.g. using a scheduled task that runs when the slave boots up) so that it's ok for Jenkins to start/stop it. ...or use the cloud functionality to start up as many of these as you like.

          pjdarton added a comment -

          No response to earlier prompt.

          pjdarton added a comment - No response to earlier prompt.
          pjdarton made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            Unassigned Unassigned
            khakunin manohar joshi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: