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

Agents not booted after Jenkins restart

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • libvirt-slave-plugin
    • None

      After upgrading the Libvirt Agents plugin from '286.vc21fa_98f531c' to '315.v5d33b_333a_551', the agents are no longer booted after a Jenkins restart and thus do not connect to the controller.  The workaround is to connect to the libvirt daemon and manually start each agent.  After that the plugin continues to operate as expected.

      Example agent Configuration as Code:

        - virtualMachineSlave:
            beforeJobSnapshotName: BuildImage
            delegateLauncher: inbound
            hypervisorDescription: QEMU+ssh - redacted.com
            labelString: Fedora-41 Fedora-prev
            launcher:
              hypervisorDescription: QEMU+ssh - redacted.com
              launcher: inbound
              timesToRetryOnFailure: 0
              virtualMachineName: Fedora-41
              waitingTimeSecs: 60
            mode: EXCLUSIVE
            name: Fedora-41
            nodeDescription: Fedora 41
            nodeProperties:
            - diskSpaceMonitor:
                freeDiskSpaceThreshold: 1GiB
                freeDiskSpaceWarningThreshold: 2GiB
                freeTempSpaceThreshold: 128 MiB
                freeTempSpaceWarningThreshold: 512MiB
            numExecutors: 1
            rebootAfterRun: true
            remoteFS: /home/redacted
            retentionStrategy: always
            shutdownMethod: shutdown
            snapshotName: BuildImage
            startupTimesToRetryOnFailure: 0
            startupWaitingPeriodSeconds: 60
            virtualMachineName: Fedora-41

            mjeanson Michael Jeanson
            wtcline_intc Wade
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: