[JENKINS-61238] Missing start function in configuration of a slave which is a virtual machine

If you select the agent management and you try to reconfigure an agent, you will not see the field startfunction if the agent is a virtual machine, which can be started over a vcenter.

If the agent is a real unix system you will see the field.

In the attachment I show the configration of 2 different agent. The agent with name "sst-j-a7w9d0" is a real server with operating system AIX 7.2. The agent will be started by SSH.

The second agent with name "sst-j-r7e7o2" is a linux virtual machine managed by a vcenter. The machine will be reset to a snapshot and then started by the vcenter. After some time (currently we wait about 5 minutes) the jenkins slave is started by SSH like the slave on AIX. But you cant't change the start method in the configuration.

If you create a new node by copying an existing you will also not be able to change the primary start method.

You are not able to change the start method to JNLP connection if the agent is a windows virtual machine with the jenkins slave installed as a windows service.

If you save the configuration of a so configured windows agent (jenkins slave as windows service) the slave will no longer be able to connect to the jenkins master, because the save removed the class of the JNLP connection in the nodes configuration file.

For instance in the "nodes/computername/config.xml" the line with the classname "hudson.slaves.JNLPLauncher" will be removed, if you save the configuration of the windows node.

true

remoting

false



false



true

VC4

sst-j-w6j0p9

true



60

NOTHING

0

---
Originally reported by rw250155, imported from: Missing start function in configuration of a slave which is a virtual machine

• assignee: peppe
  
• status: Open
  
• priority: Minor
  
• component(s): slave-setup-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 20251216-225446
  

Raw content of original issue

If you select the agent management and you try to reconfigure an agent, you will not see the field startfunction if the agent is a virtual machine, which can be started over a vcenter.

If the agent is a real unix system you will see the field.

In the attachment I show the configration of 2 different agent. The agent with name "sst-j-a7w9d0" is a real server with operating system AIX 7.2. The agent will be started by SSH.

The second agent with name "sst-j-r7e7o2" is a linux virtual machine managed by a vcenter. The machine will be reset to a snapshot and then started by the vcenter. After some time (currently we wait about 5 minutes) the jenkins slave is started by SSH like the slave on AIX. But you cant't change the start method in the configuration.

If you create a new node by copying an existing you will also not be able to change the primary start method.

You are not able to change the start method to JNLP connection if the agent is a windows virtual machine with the jenkins slave installed as a windows service.

If you save the configuration of a so configured windows agent (jenkins slave as windows service) the slave will no longer be able to connect to the jenkins master, because the save removed the class of the JNLP connection in the nodes configuration file.


For instance in the "nodes/computername/config.xml" the line with the classname "hudson.slaves.JNLPLauncher" will be removed, if you save the configuration of the windows node.


  <retentionStrategy class="hudson.slaves.RetentionStrategy$Always"/>

  <launcher class="org.jenkinsci.plugins.vSphereCloudLauncher">

    <launcher class="hudson.slaves.JNLPLauncher">

      <workDirSettings>

        <disabled>true</disabled>

        <internalDir>remoting</internalDir>

        <failIfWorkDirIsMissing>false</failIfWorkDirIsMissing>

      </workDirSettings>

      <webSocket>false</webSocket>

    </launcher>

    <overrideLaunchSupported>true</overrideLaunchSupported>

    <vsDescription>VC4</vsDescription>

    <vmName>sst-j-w6j0p9</vmName>

    <waitForVMTools>true</waitForVMTools>

    <snapName></snapName>

    <launchDelay>60</launchDelay>

    <idleAction>NOTHING</idleAction>

    <LimitedTestRunCount>0</LimitedTestRunCount>

  </launcher>

• environment: Jenkins 2.22 running on a linux machine as master

1 attachment

- [Jenkins-2.222-ConfigurationSlaves.png](https://issues.jenkins.io/secure/attachment/50423/Jenkins-2.222-ConfigurationSlaves.png)
>