[
https://issues.jenkins-ci.org/browse/JENKINS-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Gregori resolved JENKINS-8103.
-----------------------------------
Fix Version/s: current
Resolution: Fixed
Updated plugin (version 0.4.4) and works with current Jenkins version (1.451)
... see also https://issues.jenkins-ci.org/browse/JENKINS-8634
> VirtualBox plugin stopped working in recent hudson and/or VirtualBox update
> ---------------------------------------------------------------------------
>
> Key: JENKINS-8103
> URL: https://issues.jenkins-ci.org/browse/JENKINS-8103
> Project: Jenkins
> Issue Type: Bug
> Components: virtualbox
> Affects Versions: current
> Environment: Linux host with latest Hudson and VirtualBox (64bit)
> Reporter: psoetens
> Assignee: Lars Gregori
> Fix For: current
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
