[JIRA] [vsphere-cloud] (JENKINS-17095) Vsphere cloud plugin won't revert to a snapshot
michael d commented on JENKINS-17095 Vsphere cloud plugin wont revert to a snapshot I am trying to find a workaround to this. As i mentioned, when not setting a snapshot to revert to, the slave launches up and everything works fine. It's only when I specify a snapshot that this problem happen Therefor, I wonder if there's a way to revert to snapshot as a build step and not when the slave is launched ? This might be a good workaround to my problem. Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17095) Vsphere cloud plugin won't revert to a snapshot
michael d commented on JENKINS-17095 Vsphere cloud plugin wont revert to a snapshot We are using the licensed version This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17095) Vsphere cloud plugin wont revert to a snapshot
michael d created JENKINS-17095 Vsphere cloud plugin wont revert to a snapshot Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud Created: 06/Mar/13 8:31 AM Description: some background : running jenkins 1.504 and vsphere-cloud-plugin 0.10 . vsphere client 4.1.0 and ESXi 4.1.0 steps to reproduce : create a new cloud in jenkins settings create a new slave to use the cloud configured earlier with a machine name and a snapshot name to revert to on launch (force vm launch = true) test the configuration and get "Virtual Machine found successfully" launch the slave and nothing is written to the log. just the animated sphere is rolling but nothing there check with Jenkins log file : Project: Jenkins Priority: Major Reporter: michael d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17095) Vsphere cloud plugin wont revert to a snapshot
michael d
updated JENKINS-17095
Vsphere cloud plugin wont revert to a snapshot
Change By:
michael d
(06/Mar/13 8:35 AM)
Description:
somebackground:runningjenkins1.504andvsphere-cloud-plugin0.10.vsphereclient4.1.0andESXi4.1.0stepstoreproduce:createanewcloudinjenkinssettingscreateanewslavetousethecloudconfiguredearlierwithamachinenameandasnapshotnametoreverttoonlaunch(forcevmlaunch=true)testtheconfigurationandgetVirtualMachinefoundsuccessfullylaunchtheslaveandnothingiswrittentothelog.justtheanimatedsphereisrollingbutnothingtherecheckwithJenkinslogfile:
{{INFO:[vsphere]StartingVirtualMachine...}}{{Mar6,201310:20:21AMorg.jenkinsci.plugins.vSphereCloudInternalLog}}{{INFO:[vsphere]Revertingtosnapshot:michael}}{{Mar6,201310:22:21AMhudson.slaves.SlaveComputertryReconnect}}{{INFO:Attemptingtoreconnectvsphere}}{{Mar6,201310:22:21AMorg.jenkinsci.plugins.vSphereCloudInternalLog}}{{INFO:[vsphere]StartingVirtualMachine...}}{{Mar6,201310:22:21AMorg.jenkinsci.plugins.vSphereCloudInternalLog}}{{INFO:[vsphere]Revertingtosnapshot:michael}}{{Mar6,201310:24:21AMhudson.slaves.SlaveComputertryReconnect}}{{INFO:Attemptingtoreconnectvsphere}}{{Mar6,201310:24:21AMorg.jenkinsci.plugins.vSphereCloudInternalLog}}{{INFO:[vsphere]StartingVirtualMachine...}}{{Mar6,201310:24:21AMorg.jenkinsci.plugins.vSphereCloudInternalLog}}{{INFO:[vsphere]Revertingtosnapshot:michael}}{{Mar6,201310:26:21AMhudson.slaves.SlaveComputertryReconnect}}{{INFO:Attemptingtoreconnectvsphere}}{{Mar6,201310:26:21AMorg.jenkinsci.plugins.vSphereCloudInternalLog}}{{INFO:[vsphere]StartingVirtualMachine...}}{{Mar6,201310:26:21AMorg.jenkinsci.plugins.vSphereCloudInternalLog}}{{INFO:[vsphere]Revertingtosnapshot:michael}}{{Mar6,201310:28:21AMhudson.slaves.SlaveComputertryReconnect}}{{INFO:Attemptingtoreconnectvsphere}}{{Mar6,201310:28:21AMorg.jenkinsci.plugins.vSphereCloudInternalLog}}{{INFO:[vsphere]StartingVirtualMachine...}}{{Mar6,201310:28:21AMorg.jenkinsci.plugins.vSphereCloudInternalLog}}{{INFO:[vsphere]Revertingtosnapshot:michael}}{{Mar6,201310:29:01AMorg.jenkinsci.plugins.vSphereCloudInternalLog}}{{INFO:[vsphere]StartingVirtualMachine...}}{{Mar6,201310:29:02AMorg.jenkinsci.plugins.vSphereCloudInternalLog}}{{INFO:[vsphere]Revertingtosnapshot:michael}}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17095) Vsphere cloud plugin wont revert to a snapshot
michael d
updated JENKINS-17095
Vsphere cloud plugin wont revert to a snapshot
Change By:
michael d
(06/Mar/13 8:42 AM)
Description:
somebackground:runningjenkins1.504andvsphere-cloud-plugin0.10.vsphereclient4.1.0andESXi4.1.0stepstoreproduce:createanewcloudinjenkinssettingscreateanewslavetousethecloudconfiguredearlierwithamachinenameandasnapshotnametoreverttoonlaunch(forcevmlaunch=true)testtheconfigurationandgetVirtualMachinefoundsuccessfullylaunchtheslaveandnothingiswrittentothelog.justtheanimatedsphereisrollingbutnothingtherecheckwithJenkinslogfile
andseethefollowingloop
:
{{
INFO:[vsphere]StartingVirtualMachine...
}}
{{
Mar6,201310:
20
24
:21AMorg.jenkinsci.plugins.vSphereCloudInternalLog
}}
{{
INFO:[vsphere]Revertingtosnapshot:michael
}}
{{
Mar6,201310:
22
26
:21AMhudson.slaves.SlaveComputertryReconnect
}}
{{
INFO:Attemptingtoreconnectvsphere
}}
{{
Lookingatvsphereevents,icanseetheuserlogsinandlogsout,IfilookintothespecificmachineeventslistIdontseeanything.**Thishappensonlywhensettingasnapshot.withoutasnapshoteverythingworksfine.Alsotried,assuggestedbypluginowner,toSettheslavetonosnapshot.Getitrunningandconnected.Then,whileconnected,setthesnapshottoavalidvalue.Also,settheWhattodowhentheslaveisdisconnectedtoShutdownandRevert.Thendisconnecttheslave(killtheslaveagentorhitDisconnectinJenkins).SeeifboththepowerdownANDrevertcommandsaresenttotheVMbylookingatthevSpheretasklist.results:fromJenkinslogfileisee:INFO:[vsphere]Runningdisconnectprocedure...
Mar6,201310:
22
19
:
21
50
AMorg.jenkinsci.plugins.vSphereCloudInternalLog
}}
{{
INFO:[vsphere]
Starting
Shuttingdown
VirtualMachine...
}}
{{
Mar6,201310:
22
19
:
21
50
AMorg.jenkinsci.plugins.vSphereCloudInternalLog
}}
{{
INFO:[vsphere]
Revertingtosnapshot:michael}}
Poweringdownhard
{{
Mar6,201310:
24
19
:
21
50
AM
hudson
org
.
slaves
jenkinsci
.
SlaveComputertryReconnect}}
plugins.vSphereCloudInternalLog
{{
INFO:
Attemptingtoreconnect
[
vsphere
}}
]Gotanexception
{{
Mar6,201310:
24
19
:
21
50
AMorg.jenkinsci.plugins.vSphereCloudInternalLog
}}
{{
INFO:[vsphere]
StartingVirtualMachine
com
.
vmware
.
vim25
.
}}
RestrictedVersion
{{
Mar6,201310:
24
19
:
21
50
AMorg.jenkinsci.plugins.vSphereCloudInternalLog
}}
{{
INFO:[vsphere]
Revertingtosnapshot:michael}}
Printedexception
{{
Mar6,201310:
26
19
:
21
50
AMhudson.
slaves
remoting
.
SlaveComputertryReconnect}}
Channel$2handle
{{INFO
SEVERE
:
Attempting
Failed
to
reconnect
executecommandclose(channel
vsphere
}}
)
{{Mar6,201310
java.lang.NullPointerExceptionatjava.util.regex.Matcher.getTextLength(Matcher.java
:
26
1140)atjava.util.regex.Matcher.reset(Matcher.java
:
21AMorg
291)atjava
.
jenkinsci
util
.
plugins
regex
.
vSphereCloudInternalLog}}
Matcher.init(Matcher.java:211)
{{INFO
atjava.util.regex.Pattern.matcher(Pattern.java
:
[vsphere]StartingVirtualMachine
888)atjava
.
util
.
Formatter
.
}}
parse(Formatter.java:2458)
{{Mar6,201310
atjava.util.Formatter.format(Formatter.java
:
26
2414)atjava.util.Formatter.format(Formatter.java
:
21AM
2367)atjava.lang.String.format(String.java:2769)athudson.util.StreamTaskListener.fatalError(StreamTaskListener.java:153)at
org.jenkinsci.plugins.
vSphereCloudInternalLog}}
vSphereCloudLauncher.afterDisconnect(vSphereCloudLauncher.java:335)
{{INFO
athudson.slaves.SlaveComputer$2.onClosed(SlaveComputer.java
:
[vsphere]Revertingtosnapshot
419)athudson.remoting.Channel.terminate(Channel.java
:
michael}}
749)
{{
athudson.remoting.Channel$CloseCommand.execute(Channel.java:850)athudson.remoting.Channel$2.handle(Channel.java:435)athudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)
Mar6,201310:
28
19
:
21
50
AMhudson.
slaves
remoting
.
SlaveComputertryReconnect}}
Channel$2handle
{{INFO
SEVERE
:
Attemptingtoreconnectvsphere}}
Thiscommandiscreatedhere
{{Mar6,201310
Commandclosecreatedatathudson.remoting.Command.init(Command.java
:
28
56)athudson.remoting.Channel$CloseCommand.init(Channel.java
:
21AMorg
844)athudson
.
jenkinsci
remoting
.
plugins
Channel$CloseCommand
.
vSphereCloudInternalLog}}
init(Channel.java:842)
{{INFO
athudson.remoting.Channel.close(Channel.java
:
[vsphere]StartingVirtualMachine
909)athudson
.
remoting
.
Channel
.
}}
close(Channel.java:892)
{{
[JIRA] (JENKINS-17095) Vsphere cloud plugin wont revert to a snapshot
michael d
updated JENKINS-17095
Vsphere cloud plugin wont revert to a snapshot
Change By:
michael d
(06/Mar/13 8:45 AM)
Description:
somebackground:runningjenkins1.504andvsphere-cloud-plugin0.10.vsphereclient4.1.0andESXi4.1.0stepstoreproduce:createanewcloudinjenkinssettingscreateanewslavetousethecloudconfiguredearlierwithamachinenameandasnapshotnametoreverttoonlaunch(forcevmlaunch=true)testtheconfigurationandgetVirtualMachinefoundsuccessfullylaunchtheslaveandnothingiswrittentothelog.justtheanimatedsphereisrollingbutnothingthere**Thishappensonlywhensettingasnapshot.withoutasnapshoteverythingworksfine.checkwithJenkinslogfileandseethefollowingloop:{noformat}INFO:[vsphere]StartingVirtualMachine...Mar6,201310:24:21AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]Revertingtosnapshot:michaelMar6,201310:26:21AMhudson.slaves.SlaveComputertryReconnectINFO:Attemptingtoreconnectvsphere{noformat}Lookingatvsphereevents,icanseetheuserlogsinandlogsout,IfilookintothespecificmachineeventslistIdontseeanything.Alsotried,assuggestedbypluginowner,toSettheslavetonosnapshot.Getitrunningandconnected.Then,whileconnected,setthesnapshottoavalidvalue.Also,settheWhattodowhentheslaveisdisconnectedtoShutdownandRevert.Thendisconnecttheslave(killtheslaveagentorhitDisconnectinJenkins).SeeifboththepowerdownANDrevertcommandsaresenttotheVMbylookingatthevSpheretasklist.results:fromJenkinslogfileisee:
{noformat}
INFO:[vsphere]Runningdisconnectprocedure...Mar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]ShuttingdownVirtualMachine...Mar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]PoweringdownhardMar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]GotanexceptionMar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]com.vmware.vim25.RestrictedVersionMar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]PrintedexceptionMar6,201310:19:50AMhudson.remoting.Channel$2handleSEVERE:Failedtoexecutecommandclose(channelvsphere)java.lang.NullPointerExceptionatjava.util.regex.Matcher.getTextLength(Matcher.java:1140)atjava.util.regex.Matcher.reset(Matcher.java:291)atjava.util.regex.Matcher.init(Matcher.java:211)atjava.util.regex.Pattern.matcher(Pattern.java:888)atjava.util.Formatter.parse(Formatter.java:2458)atjava.util.Formatter.format(Formatter.java:2414)atjava.util.Formatter.format(Formatter.java:2367)atjava.lang.String.format(String.java:2769)athudson.util.StreamTaskListener.fatalError(StreamTaskListener.java:153)atorg.jenkinsci.plugins.vSphereCloudLauncher.afterDisconnect(vSphereCloudLauncher.java:335)athudson.slaves.SlaveComputer$2.onClosed(SlaveComputer.java:419)athudson.remoting.Channel.terminate(Channel.java:749)athudson.remoting.Channel$CloseCommand.execute(Channel.java:850)athudson.remoting.Channel$2.handle(Channel.java:435)athudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)Mar6,201310:19:50AMhudson.remoting.Channel$2handleSEVERE:ThiscommandiscreatedhereCommandclosecreatedatathudson.remoting.Command.init(Command.java:56)athudson.remoting.Channel$CloseCommand.init(Channel.java:844)athudson.remoting.Channel$CloseCommand.init(Channel.java:842)athudson.remoting.Channel.close(Channel.java:909)athudson.remoting.Channel.close(Channel.java:892)athudson.remoting.Channel$CloseCommand.execute(Channel.java:849)athudson.remoting.Channel$2.handle(Channel.java:435)athudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)Mar6,201310:20:21AMhudson.slaves.SlaveComputertryReconnectINFO:AttemptingtoreconnectvsphereMar6,201310:20:21AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]StartingVirtualMachine...Mar6,201310:20:21AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]Revertingtosnapshot:michael
{noformat}
fromthevsphereeventlistidontseetheshutdowneventorthesnapshot
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more
[JIRA] (JENKINS-17095) Vsphere cloud plugin wont revert to a snapshot
michael d updated JENKINS-17095 Vsphere cloud plugin wont revert to a snapshot Change By: michael d (06/Mar/13 8:46 AM) Affects Version/s: current Environment: runningjenkins1.504andvsphere-cloud-plugin0.10.vsphereclient4.1.0andESXi4.1.0 Description: somebackground:runningjenkins1.504andvsphere-cloud-plugin0.10.vsphereclient4.1.0andESXi4.1.0
[JIRA] (JENKINS-17095) Vsphere cloud plugin wont revert to a snapshot
michael d
updated JENKINS-17095
Vsphere cloud plugin wont revert to a snapshot
Change By:
michael d
(06/Mar/13 8:44 AM)
Description:
somebackground:runningjenkins1.504andvsphere-cloud-plugin0.10.vsphereclient4.1.0andESXi4.1.0stepstoreproduce:createanewcloudinjenkinssettingscreateanewslavetousethecloudconfiguredearlierwithamachinenameandasnapshotnametoreverttoonlaunch(forcevmlaunch=true)testtheconfigurationandgetVirtualMachinefoundsuccessfullylaunchtheslaveandnothingiswrittentothelog.justtheanimatedsphereisrollingbutnothingthere
**Thishappensonlywhensettingasnapshot.withoutasnapshoteverythingworksfine.
checkwithJenkinslogfileandseethefollowingloop:
{noformat}
INFO:[vsphere]StartingVirtualMachine...Mar6,201310:24:21AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]Revertingtosnapshot:michaelMar6,201310:26:21AMhudson.slaves.SlaveComputertryReconnectINFO:Attemptingtoreconnectvsphere
{noformat}
Lookingatvsphereevents,icanseetheuserlogsinandlogsout,IfilookintothespecificmachineeventslistIdontseeanything.
**Thishappensonlywhensettingasnapshot.withoutasnapshoteverythingworksfine.
Alsotried,assuggestedbypluginowner,toSettheslavetonosnapshot.Getitrunningandconnected.Then,whileconnected,setthesnapshottoavalidvalue.Also,settheWhattodowhentheslaveisdisconnectedtoShutdownandRevert.Thendisconnecttheslave(killtheslaveagentorhitDisconnectinJenkins).SeeifboththepowerdownANDrevertcommandsaresenttotheVMbylookingatthevSpheretasklist.results:fromJenkinslogfileisee:INFO:[vsphere]Runningdisconnectprocedure...Mar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]ShuttingdownVirtualMachine...Mar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]PoweringdownhardMar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]GotanexceptionMar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]com.vmware.vim25.RestrictedVersionMar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]PrintedexceptionMar6,201310:19:50AMhudson.remoting.Channel$2handleSEVERE:Failedtoexecutecommandclose(channelvsphere)java.lang.NullPointerExceptionatjava.util.regex.Matcher.getTextLength(Matcher.java:1140)atjava.util.regex.Matcher.reset(Matcher.java:291)atjava.util.regex.Matcher.init(Matcher.java:211)atjava.util.regex.Pattern.matcher(Pattern.java:888)atjava.util.Formatter.parse(Formatter.java:2458)atjava.util.Formatter.format(Formatter.java:2414)atjava.util.Formatter.format(Formatter.java:2367)atjava.lang.String.format(String.java:2769)athudson.util.StreamTaskListener.fatalError(StreamTaskListener.java:153)atorg.jenkinsci.plugins.vSphereCloudLauncher.afterDisconnect(vSphereCloudLauncher.java:335)athudson.slaves.SlaveComputer$2.onClosed(SlaveComputer.java:419)athudson.remoting.Channel.terminate(Channel.java:749)athudson.remoting.Channel$CloseCommand.execute(Channel.java:850)athudson.remoting.Channel$2.handle(Channel.java:435)athudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)Mar6,201310:19:50AMhudson.remoting.Channel$2handleSEVERE:ThiscommandiscreatedhereCommandclosecreatedatathudson.remoting.Command.init(Command.java:56)athudson.remoting.Channel$CloseCommand.init(Channel.java:844)athudson.remoting.Channel$CloseCommand.init(Channel.java:842)athudson.remoting.Channel.close(Channel.java:909)athudson.remoting.Channel.close(Channel.java:892)athudson.remoting.Channel$CloseCommand.execute(Channel.java:849)athudson.remoting.Channel$2.handle(Channel.java:435)athudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)Mar6,201310:20:21AMhudson.slaves.SlaveComputertryReconnectINFO:AttemptingtoreconnectvsphereMar6,201310:20:21AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]StartingVirtualMachine...Mar6,201310:20:21AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]Revertingtosnapshot:michaelfromthevsphereeventlistidontseetheshutdowneventorthesnapshot
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please
[JIRA] (JENKINS-17095) Vsphere cloud plugin wont revert to a snapshot
michael d updated JENKINS-17095 Vsphere cloud plugin wont revert to a snapshot Change By: michael d (06/Mar/13 8:47 AM) Environment: running Running jenkins1.504 onRHEL5 andvsphere-cloud-plugin0.10.vsphereclient4.1.0andESXi4.1.0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17095) Vsphere cloud plugin wont revert to a snapshot
michael d
updated JENKINS-17095
Vsphere cloud plugin wont revert to a snapshot
Change By:
michael d
(06/Mar/13 8:48 AM)
Description:
steps
Steps
toreproduce:
*
createanewcloudinjenkinssettings
*
createanewslavetousethecloudconfiguredearlierwithamachinename
*
andasnapshotnametoreverttoonlaunch(forcevmlaunch=true)
*
testtheconfigurationandgetVirtualMachinefoundsuccessfully
*
launchtheslaveandnothingiswrittentothelog.justtheanimatedsphereisrollingbutnothingthere*
*
Note:
Thishappensonlywhensettingasnapshot.withoutasnapshoteverythingworksfine.checkwithJenkinslogfileandseethefollowingloop:{noformat}INFO:[vsphere]StartingVirtualMachine...Mar6,201310:24:21AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]Revertingtosnapshot:michaelMar6,201310:26:21AMhudson.slaves.SlaveComputertryReconnectINFO:Attemptingtoreconnectvsphere{noformat}Lookingatvsphereevents,icanseetheuserlogsinandlogsout,IfilookintothespecificmachineeventslistIdontseeanything.Alsotried,assuggestedbypluginowner,toSettheslavetonosnapshot.Getitrunningandconnected.Then,whileconnected,setthesnapshottoavalidvalue.Also,settheWhattodowhentheslaveisdisconnectedtoShutdownandRevert.Thendisconnecttheslave(killtheslaveagentorhitDisconnectinJenkins).SeeifboththepowerdownANDrevertcommandsaresenttotheVMbylookingatthevSpheretasklist.results:fromJenkinslogfileisee:{noformat}INFO:[vsphere]Runningdisconnectprocedure...Mar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]ShuttingdownVirtualMachine...Mar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]PoweringdownhardMar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]GotanexceptionMar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]com.vmware.vim25.RestrictedVersionMar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]PrintedexceptionMar6,201310:19:50AMhudson.remoting.Channel$2handleSEVERE:Failedtoexecutecommandclose(channelvsphere)java.lang.NullPointerExceptionatjava.util.regex.Matcher.getTextLength(Matcher.java:1140)atjava.util.regex.Matcher.reset(Matcher.java:291)atjava.util.regex.Matcher.init(Matcher.java:211)atjava.util.regex.Pattern.matcher(Pattern.java:888)atjava.util.Formatter.parse(Formatter.java:2458)atjava.util.Formatter.format(Formatter.java:2414)atjava.util.Formatter.format(Formatter.java:2367)atjava.lang.String.format(String.java:2769)athudson.util.StreamTaskListener.fatalError(StreamTaskListener.java:153)atorg.jenkinsci.plugins.vSphereCloudLauncher.afterDisconnect(vSphereCloudLauncher.java:335)athudson.slaves.SlaveComputer$2.onClosed(SlaveComputer.java:419)athudson.remoting.Channel.terminate(Channel.java:749)athudson.remoting.Channel$CloseCommand.execute(Channel.java:850)athudson.remoting.Channel$2.handle(Channel.java:435)athudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)Mar6,201310:19:50AMhudson.remoting.Channel$2handleSEVERE:ThiscommandiscreatedhereCommandclosecreatedatathudson.remoting.Command.init(Command.java:56)athudson.remoting.Channel$CloseCommand.init(Channel.java:844)athudson.remoting.Channel$CloseCommand.init(Channel.java:842)athudson.remoting.Channel.close(Channel.java:909)athudson.remoting.Channel.close(Channel.java:892)athudson.remoting.Channel$CloseCommand.execute(Channel.java:849)athudson.remoting.Channel$2.handle(Channel.java:435)athudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)Mar6,201310:20:21AMhudson.slaves.SlaveComputertryReconnectINFO:AttemptingtoreconnectvsphereMar6,201310:20:21AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]StartingVirtualMachine...Mar6,201310:20:21AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]Revertingtosnapshot:michael{noformat}fromthevsphereeventlistidontseetheshutdowneventorthesnapshot
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-17095) Vsphere cloud plugin wont revert to a snapshot
michael d
updated JENKINS-17095
Vsphere cloud plugin wont revert to a snapshot
Change By:
michael d
(06/Mar/13 8:49 AM)
Description:
Stepstoreproduce:*
create
Create
anewcloudinjenkinssettings*
create
Create
anewslavetousethecloudconfiguredearlierwithamachinename*
and
And
asnapshotnametoreverttoonlaunch(forcevmlaunch=true)*
test
Test
theconfigurationandgetVirtualMachinefoundsuccessfully*
launch
Launch
theslaveandnothingiswrittentothelog.justtheanimatedsphereisrollingbutnothingthere*Note:Thishappensonlywhensettingasnapshot.withoutasnapshoteverythingworksfine.
check
Check
withJenkinslogfileandseethefollowingloop:{noformat}INFO:[vsphere]StartingVirtualMachine...Mar6,201310:24:21AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]Revertingtosnapshot:michaelMar6,201310:26:21AMhudson.slaves.SlaveComputertryReconnectINFO:Attemptingtoreconnectvsphere{noformat}Lookingatvsphereevents,
i
I
canseetheuserlogsinandlogsout,If
i
I
lookintothespecificmachineeventslistIdontseeanything.Alsotried,assuggestedbypluginowner,toSettheslavetonosnapshot.Getitrunningandconnected.Then,whileconnected,setthesnapshottoavalidvalue.Also,settheWhattodowhentheslaveisdisconnectedtoShutdownandRevert.Thendisconnecttheslave(killtheslaveagentorhitDisconnectinJenkins).SeeifboththepowerdownANDrevertcommandsaresenttotheVMbylookingatthevSpheretasklist.
results
Results
:fromJenkinslogfileisee:{noformat}INFO:[vsphere]Runningdisconnectprocedure...Mar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]ShuttingdownVirtualMachine...Mar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]PoweringdownhardMar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]GotanexceptionMar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]com.vmware.vim25.RestrictedVersionMar6,201310:19:50AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]PrintedexceptionMar6,201310:19:50AMhudson.remoting.Channel$2handleSEVERE:Failedtoexecutecommandclose(channelvsphere)java.lang.NullPointerExceptionatjava.util.regex.Matcher.getTextLength(Matcher.java:1140)atjava.util.regex.Matcher.reset(Matcher.java:291)atjava.util.regex.Matcher.init(Matcher.java:211)atjava.util.regex.Pattern.matcher(Pattern.java:888)atjava.util.Formatter.parse(Formatter.java:2458)atjava.util.Formatter.format(Formatter.java:2414)atjava.util.Formatter.format(Formatter.java:2367)atjava.lang.String.format(String.java:2769)athudson.util.StreamTaskListener.fatalError(StreamTaskListener.java:153)atorg.jenkinsci.plugins.vSphereCloudLauncher.afterDisconnect(vSphereCloudLauncher.java:335)athudson.slaves.SlaveComputer$2.onClosed(SlaveComputer.java:419)athudson.remoting.Channel.terminate(Channel.java:749)athudson.remoting.Channel$CloseCommand.execute(Channel.java:850)athudson.remoting.Channel$2.handle(Channel.java:435)athudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)Mar6,201310:19:50AMhudson.remoting.Channel$2handleSEVERE:ThiscommandiscreatedhereCommandclosecreatedatathudson.remoting.Command.init(Command.java:56)athudson.remoting.Channel$CloseCommand.init(Channel.java:844)athudson.remoting.Channel$CloseCommand.init(Channel.java:842)athudson.remoting.Channel.close(Channel.java:909)athudson.remoting.Channel.close(Channel.java:892)athudson.remoting.Channel$CloseCommand.execute(Channel.java:849)athudson.remoting.Channel$2.handle(Channel.java:435)athudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)Mar6,201310:20:21AMhudson.slaves.SlaveComputertryReconnectINFO:AttemptingtoreconnectvsphereMar6,201310:20:21AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]StartingVirtualMachine...Mar6,201310:20:21AMorg.jenkinsci.plugins.vSphereCloudInternalLogINFO:[vsphere]Revertingtosnapshot:michael{noformat}
from
From
thevsphereeventlistidontseetheshutdowneventorthesnapshot
URL:
https://wiki.jenkins-ci.org/display/JENKINS/vSphere+Cloud+Plugin?focusedCommentId=66847166#comment-66847166
[JIRA] (JENKINS-17095) Vsphere cloud plugin won't revert to a snapshot
michael d updated JENKINS-17095 Vsphere cloud plugin wont revert to a snapshot Change By: michael d (06/Mar/13 8:57 AM) Summary: Vspherecloudplugin wont wont reverttoasnapshot This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
michael d commented on JENKINS-15156 Builds disappear from build history after completion Also experiencing this in 1.499 on RHEL. Reloading configuration from disk seems to solve it. Can't find any pattern to reproduce this, and the logs doesn't say anything. Voodoo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16203) Jenkins tools auto install dir has changed
michael d commented on JENKINS-16203 Jenkins tools auto install dir has changed Can I tell Jenkins to auto deploy my custom zipped tool to slaves ? I wasn't aware of this solution, if so, it is much better solution than what i used This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16203) Jenkins tools auto install dir has changed
michael d created JENKINS-16203 Jenkins tools auto install dir has changed Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 27/Dec/12 9:13 AM Description: After upgrading from 1.491 to 1.495 I've noticed that Jenkins tries to install tools in the following directories : JDK: $JENKINS_HOME/tools/hudson.model.JDK/ instead of $JENKINS_HOME/tools/JDK/ Ant: $JENKINS_HOME/tools/hudson.tasks.Ant_AntInstallation instead of $JENKINS_HOME/tools/ANT Maven: $JENKINS_HOME/tools/hudson.tasks.Maven_MavenInstallation instead of $JENKINS_HOME/tools/Maven I have these plugins installed : Jenkins Mailer Plugin External Monitor Job Type Plugin LDAP Plugin pam-auth ant javadoc Claim Plugin Role-based Authorization Strategy Show Build Parameters plugin Jenkins description setter plugin Console Column Plugin Token Macro Plugin Maven Integration plugin Jenkins CVS Plug-in Jenkins Subversion Plug-in Jenkins Multiple SCMs plugin Jenkins Parameterized Trigger plugin Jenkins GIT plugin Static Analysis Utilities Jenkins Email Extension Plugin View Job Filters ThinBackup Jenkins Workspace Cleanup Plugin HTML Audio Notifier Copy Artifact Plugin Jenkins SSH Slaves plugin Warnings Plug-in vSphere Cloud Plugin Monitoring Publish Over SSH Run Condition Plugin conditional-buildstep Jenkins Job Configuration History Plugin Jenkins Artifact Deployer Plug-in Green Balls Jenkins Translation Assistance plugin Jenkins disk-usage plugin NAnt Plugin Jenkins Clone Workspace SCM Plug-in Jenkins Sonar Plugin FindBugs Plug-in Environment Injector Plugin HTML Publisher plugin Environment: RHEL 5.5 Project: Jenkins Priority: Blocker Reporter: michael d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11519) When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than '@'
michael d edited a comment on JENKINS-11519 When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than @ I think the change needed to be done in class WorkspaceList : /** * The token that combines the project name and unique number to create unique workspace directory. */ private static final String COMBINATOR = System.getProperty(WorkspaceList.class.getName(),"@"); This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11519) When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than '@'
michael d commented on JENKINS-11519 When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than @ I think the change needed to be done in class WorkspaceList : /** * The token that combines the project name and unique number to create unique workspace directory. */ private static final String COMBINATOR = System.getProperty(WorkspaceList.class.getName(),"@"); I've seen kohsuke mention in the commit message that advanced users can change this string somehow, not sure how though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11519) When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than '@'
michael d commented on JENKINS-11519 When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than @ According to someone on IRC, the workaround is this : You need to add a -D parameter to the startup of jenkins : -Djava.hudson.slaves.WorkspaceList=! (to change it to ! for example) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11519) When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than '@'
michael d edited a comment on JENKINS-11519 When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than @ According to darkrift on IRC, the workaround is this : You need to add a -D parameter to the startup of jenkins : -Djava.hudson.slaves.WorkspaceList=! (to change it to ! for example) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11519) When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than '@'
michael d edited a comment on JENKINS-11519 When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than @ According to darkrift on IRC, the workaround is this : You need to add a -D parameter to the startup of jenkins : -Dhudson.slaves.WorkspaceList=! (to change it to ! for example) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11519) When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than '@'
[
https://issues.jenkins-ci.org/browse/JENKINS-11519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael d updated JENKINS-11519:
Priority: Major (was: Minor)
When chosing Execute concurrent builds if necessary extra workspaces
created should use a different character than '@'
Key: JENKINS-11519
URL: https://issues.jenkins-ci.org/browse/JENKINS-11519
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Reporter: michael d
When choosing in build setting the option {{Execute concurrent builds if
necessary}}, if a build is executed while another build is running, the
second workspace created as {{workspace@2}}.
The use of '@' character is not so good as it is sometimes used as a
meta-character in scripts.
For example, I had a problem when my script was trying to run sqlplus command
where @ is used.
Consider changing '@' character with '_' or simply just using {{workspace2}}
with no character in between.
--
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
[JIRA] (JENKINS-11519) When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than '@'
[
https://issues.jenkins-ci.org/browse/JENKINS-11519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162479#comment-162479
]
michael d commented on JENKINS-11519:
-
If this is not going to be changed, is there any way to change it manually in a
conf file somehow ?
When chosing Execute concurrent builds if necessary extra workspaces
created should use a different character than '@'
Key: JENKINS-11519
URL: https://issues.jenkins-ci.org/browse/JENKINS-11519
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Reporter: michael d
When choosing in build setting the option {{Execute concurrent builds if
necessary}}, if a build is executed while another build is running, the
second workspace created as {{workspace@2}}.
The use of '@' character is not so good as it is sometimes used as a
meta-character in scripts.
For example, I had a problem when my script was trying to run sqlplus command
where @ is used.
Consider changing '@' character with '_' or simply just using {{workspace2}}
with no character in between.
--
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
[JIRA] (JENKINS-13692) Clicking back button in browser on trend page gives unexpected token ) error
michael d created JENKINS-13692:
---
Summary: Clicking back button in browser on trend page gives
unexpected token ) error
Key: JENKINS-13692
URL: https://issues.jenkins-ci.org/browse/JENKINS-13692
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Environment: Using windows 7 64bit with latest chrome browser
Reporter: michael d
Attachments: Capture.PNG
When you go into a job's trend page and click the back button in the browser
you get the following error:
{quote}SyntaxError: Unexpected token ){quote}
Image attached.
--
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
