[JIRA] [openstack-cloud-plugin] (JENKINS-34495) Plugin fails to resolve image ID
Title: Message Title Jaap Coomans commented on JENKINS-34495 Re: Plugin fails to resolve image ID Great! Thank you for the quick response and release Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [openstack-cloud-plugin] (JENKINS-34495) Plugin fails to resolve image ID
Title: Message Title Jaap Coomans commented on JENKINS-34495 Re: Plugin fails to resolve image ID Thank you for the quick response Oliver Gondža. I tried to run the script for both ACTIVE and active and the result is as I expected based on my earlier findings: ACTIVE: Returns Result: [] active: Returns a list of all 6 available images Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [openstack-cloud-plugin] (JENKINS-34495) Plugin fails to resolve image ID
Title: Message Title Jaap Coomans created an issue Jenkins / JENKINS-34495 Plugin fails to resolve image ID Issue Type: Bug Assignee: Oliver Gondža Components: openstack-cloud-plugin Created: 2016/Apr/28 12:45 PM Environment: Jenkins v1.609.1 OpenStack Cloud plugin v2.3 OS: SLES 11 SP3 Priority: Major Reporter: Jaap Coomans I've set up and configured the OpenStack Cloud plugin with one template. When I try to launch a slave based on that template (via Manage nodes) all I get is: "Error. Boot failed". After studying the logs and the network traffic I found the cause. The plugin tries to resolve the image ID based on the Image name that I configured. (See {{jenkins.plugins.openstack.compute.internal.OpenStack.getImageIdFor(String name)}). This results is an API call to the images API: HTTP/1.1 GET v1/images?status=ACTIVE=My_Image The API however expects a lowercase status instead of uppercase (see also http://developer.openstack.org/api-ref-image-v1.html). So the response body is: {"images": []}. The result of this is that the plugin tries to provision an instance via the API without providing an imageRef. So there are essentially two issues: 1. The plugin makes the wrong API call 2. The plugin doesn't
[JIRA] [weblogic-deployer-plugin] (JENKINS-21244) Un-escaped $ in module file name passed in command line to weblogic.jar results in the input file not found deployer
Jaap Coomans commented on JENKINS-21244 Un-escaped $ in module file name passed in command line to weblogic.jar results in the input file not found deployer Thank you for the very quick response and resolution! 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/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-21244) Un-escaped $ in module file name passed in command line to weblogic.jar results in the input file not found deployer
Jaap Coomans commented on JENKINS-21244 Un-escaped $ in module file name passed in command line to weblogic.jar results in the input file not found deployer A "fix" for this issue broke the functionality of the plugin for me. In src/main/java/org/jenkinsci/plugins/deploy/weblogic/deployer/WebLogicDeployer.java the following line is added: args.add("\""+ parameter.getSource()+"\""); The result is that the source parameter is passed with two pairs of quotes (""/path/to/file""), of which the inner pair remains in the String that is being processed by the WebLogic deployer. This finally results in a FileNotFoundException: java.io.FileNotFoundException: /"/var/opt/jenkins/workspace/sample-project/target/sample-project-0.1.0-SNAPSHOT.war" (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:131) at weblogic.utils.FileUtils.copy(FileUtils.java:266) at weblogic.utils.FileUtils.copy(FileUtils.java:245) at weblogic.utils.FileUtils.copy(FileUtils.java:186) at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.upload(ServerConnectionImpl.java:849) at weblogic.deploy.api.spi.deploy.internal.BasicOperation.uploadFiles(BasicOperation.java:332) at weblogic.deploy.api.spi.deploy.internal.BasicOperation.execute(BasicOperation.java:465) at weblogic.deploy.api.spi.deploy.internal.BasicOperation.run(BasicOperation.java:178) at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.deploy(WebLogicDeploymentManagerImpl.java:390) at weblogic.deploy.api.tools.deployer.DeployOperation.execute(DeployOperation.java:51) at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:139) at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88) at weblogic.utils.compiler.Tool.run(Tool.java:158) at weblogic.utils.compiler.Tool.run(Tool.java:115) at weblogic.Deployer.run(Deployer.java:74) at weblogic.Deployer.main(Deployer.java:55) 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/d/optout.