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

VirtualBox plugin stopped working in recent hudson and/or VirtualBox update

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: virtualbox-plugin
    • Labels:
      None
    • Environment:
      Linux host with latest Hudson and VirtualBox (64bit)
    • Similar Issues:

      Description

      This plugin stopped working after a VBox upgrade or (more likely) Hudson upgrade.
      I can still test the connection in the 'Cloud setup' section, vboxwebsrv logs acknowledge the connection from Hudson and Hudson reports 'Success'. The virtual machine is however not started when it should. It looks like the plugin thinks there are no virtual machines available.

      The dropdown box 'Virtual Machine Name' of the Virtual node's configuration page remains empty, and no messages appear in the vboxwebsrv. It appears like the plugin is no longer called from Hudson (or no longer calls the vboxwebsrv), or that some web page form callback handler is not called.

      It's probably a trivial fix, but the plugin is now clearly broken, while it still worked about two months ago.

        Attachments

          Activity

          Hide
          choas Lars Gregori added a comment -

          Updated plugin (version 0.4.4) and works with current Jenkins version (1.451) ... see also https://issues.jenkins-ci.org/browse/JENKINS-8634

          Show
          choas Lars Gregori added a comment - Updated plugin (version 0.4.4) and works with current Jenkins version (1.451) ... see also https://issues.jenkins-ci.org/browse/JENKINS-8634

            People

            • Assignee:
              choas Lars Gregori
              Reporter:
              psoetens psoetens
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: