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

fsRoot gets reset on save

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • ec2-fleet-plugin
    • None
    • jenkins version: 2.46.1 ec2-spot-fleet version: 1.1.2

      When setting the Jenkins Filesystem Root for the spot fleet, saving it and reopening the general settings the box for Jenkins Filesystem Root is empty again. When checking the config.xml on the jenkins master itself we noticed that when its is saved the first time, it gets set correctly. But when opening the general config and not entering any value in the filesystem root box, the fsRoot in the config.xml gets reset. 

      This is what it looks like when we save after putting in the value for Jenkins Filesystem Root

       

      <clouds>
      <com.amazon.jenkins.ec2fleet.EC2FleetCloud plugin="ec2-fleet@1.1.2">
      <name>FleetCloud</name>
      <fsRoot>/workspace/jenkins</fsRoot>
      <computerConnector class="hudson.plugins.sshslaves.SSHConnector" plugin="ssh-slaves@1.17">
      <port>22</port>
      <credentialsId>nodekey</credentialsId>
      <jvmOptions></jvmOptions>
      <javaPath>/home/jenkins/java/bin/java</javaPath>
      <launchTimeoutSeconds>60</launchTimeoutSeconds>
      <maxNumRetries>10000</maxNumRetries>
      <retryWaitTime>5</retryWaitTime>
      <sshHostKeyVerificationStrategy class="hudson.plugins.sshslaves.verifiers.NonVerifyingKeyVerificationStrategy"/>
      </computerConnector>
      <privateIpUsed>true</privateIpUsed>
      <labelString>jenkins-fleet</labelString>
      <idleMinutes>30</idleMinutes>
      <minSize>3</minSize>
      <maxSize>10</maxSize>
      <numExecutors>3</numExecutors>
      <status>
      <numActive>0</numActive>
      <numDesired>0</numDesired>
      <state>Initializing</state>
      <instances class="empty-set"/>
      <label>jenkins-fleet</label>
      </status>
      <plannedNodes/>
      <instancesSeen/>
      <instancesDying/>
      </com.amazon.jenkins.ec2fleet.EC2FleetCloud>
      </clouds>
      

       

       

      This is what the config.xml looks like after just opening and saving the general config without changing anything

      <clouds>
      <com.amazon.jenkins.ec2fleet.EC2FleetCloud plugin="ec2-fleet@1.1.2">
      <name>FleetCloud</name>
      <fsRoot></fsRoot>
      <computerConnector class="hudson.plugins.sshslaves.SSHConnector" plugin="ssh-slaves@1.17">
      <port>22</port>
      <credentialsId>nodekey</credentialsId>
      <jvmOptions></jvmOptions>
      <javaPath>/home/jenkins/java/bin/java</javaPath>
      <launchTimeoutSeconds>60</launchTimeoutSeconds>
      <maxNumRetries>10000</maxNumRetries>
      <retryWaitTime>5</retryWaitTime>
      <sshHostKeyVerificationStrategy class="hudson.plugins.sshslaves.verifiers.NonVerifyingKeyVerificationStrategy"/>
      </computerConnector>
      <privateIpUsed>true</privateIpUsed>
      <labelString>jenkins-fleet</labelString>
      <idleMinutes>30</idleMinutes>
      <minSize>3</minSize>
      <maxSize>10</maxSize>
      <numExecutors>3</numExecutors>
      <status>
      <numActive>0</numActive>
      <numDesired>0</numDesired>
      <state>Initializing</state>
      <instances class="empty-set"/>
      <label>jenkins-fleet</label>
      </status>
      <plannedNodes/>
      <instancesSeen/>
      <instancesDying/>
      </com.amazon.jenkins.ec2fleet.EC2FleetCloud>
      </clouds>
      
      

      If you need any more information please let me know.

            daenor Tomas Vercautter
            daenor Tomas Vercautter
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: