-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins ver. 2.46.2
Vsphere Plugin 2.18
Hi,
I created a job to migrate a Template in VM.
I configured the plugin like this :
VSphere Action : Convert Template to a VM
Template , Cluster and Resource Pool are filled correctly.
( Note, the template has been generated by another job with the VSphere action : Convert VM to a Template that work fine )
The job returns sucess but doesn't work, I dont see any interaction with vsphere. there is no task created in Vsphere.
In the console output I have :
Started by user Philippe
[EnvInject] - Loading node environment variables.
Building on master in workspace /localdata/tc/current/var/Jenkins/COFLIGHT_SYSTEM/workspace/VMW_CREATE_VM_FROM_TEMPLATE
[vSphere]
[vSphere] Performing vSphere build step: "Convert template to a VM"
[vSphere] Attempting to use server configuration: "Vsphere_Cloud"
[vSphere] Converting template to VM. Please wait ...
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Finished: SUCCESS
How can I have more traces / logs to understand the problem ?
Is it an known bug ?
- is related to
-
-
- Open
-
[JENKINS-56884] Vsphere plugin : Convert Template to a VM
pjdarton
added a comment - I'd suggest that you log the following at Log level "ALL":
- vsphere-cloud
- org.jenkinsci.plugins.folder.FolderVSphereCloudProperty
- org.jenkinsci.plugins.vsphere
- org.jenkinsci.plugins.vSphereCloud
- org.jenkinsci.plugins.vSphereCloudLauncher
- org.jenkinsci.plugins.vSphereCloudProvisionedSlave
- org.jenkinsci.plugins.vSphereCloudRunListener
- org.jenkinsci.plugins.vSphereCloudSlave
- org.jenkinsci.plugins.vSphereCloudSlaveComputer
- org.jenkinsci.plugins.vSphereCloudSlaveTemplate
- org.jenkinsci.plugins.workflow.vSphereStep
FYI logging on this plugin is a bit odd "for historical reasons", i.e. it was like that well before I ever got involved and I (and everyone else who's contributed since) have left that bit alone.
Fixing it would be non-trivial, as it would mean moving all the code into a deeper package (e.g. org.jenkinsci.plugins.vsphere) and renaming the classes so they're called "VSphere..." instead of "vSphere...", but then there'd be hell to pay w.r.t. handling the upgrade path and (thus far) nobody's had the courage, the skill and the inclination to do that.
Note: It's not a known bug - we turn VMs to templates and templates to VMs where I work and "it works for us" - but there is a known bug whereby most (all?) of the build steps will declare "success" if they fail- my guess is that it's failing silently and you'll see the real error once you've got more logging enabled.
pjdarton
added a comment - I'd suggest that you log the following at Log level "ALL":
vsphere-cloud
org.jenkinsci.plugins.folder.FolderVSphereCloudProperty
org.jenkinsci.plugins.vsphere
org.jenkinsci.plugins.vSphereCloud
org.jenkinsci.plugins.vSphereCloudLauncher
org.jenkinsci.plugins.vSphereCloudProvisionedSlave
org.jenkinsci.plugins.vSphereCloudRunListener
org.jenkinsci.plugins.vSphereCloudSlave
org.jenkinsci.plugins.vSphereCloudSlaveComputer
org.jenkinsci.plugins.vSphereCloudSlaveTemplate
org.jenkinsci.plugins.workflow.vSphereStep
FYI logging on this plugin is a bit odd "for historical reasons", i.e. it was like that well before I ever got involved and I (and everyone else who's contributed since) have left that bit alone.
Fixing it would be non-trivial, as it would mean moving all the code into a deeper package (e.g. org.jenkinsci.plugins.vsphere ) and renaming the classes so they're called " VSphere ..." instead of " vSphere ...", but then there'd be hell to pay w.r.t. handling the upgrade path and (thus far) nobody's had the courage, the skill and the inclination to do that.
Note: It's not a known bug - we turn VMs to templates and templates to VMs where I work and "it works for us" - but there is a known bug whereby most (all?) of the build steps will declare "success" if they fail- my guess is that it's failing silently and you'll see the real error once you've got more logging enabled.
I added a logger on all org.jenkinsci.plugins.vsphere* library with the level ALL ... nothing is written when I use the action Convert Template to a VM
The logger works fine as I have some log inputs when I call a job that do a POWER ON on a VM .