[ https://issues.jboss.org/browse/JBIDE-10502?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-10502: ---------------------------------------- Fix Version/s: 3.3.0.Beta1 (was: 3.3.0.M5) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10502?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-10502: ------------------------------------ I assume yes. I selected the jenkins-client checkbox and then the wizard asked me to enter jenkins app name. Then it automatically started to install jenkins server app. After that I got the notification about credentials and that the jenkins was installed successfully. Then it returned to the wizard with the embedded cartridges list. It fails at the final step if I click on finish. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10502?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10502 at 12/16/11 11:53 AM: --------------------------------------------------------------------- I tried to reproduce this and could not. things went perfectly well here, I tried several times. The error log shows the following error: {code} Caused by: org.jboss.tools.openshift.express.internal.client.httpclient.InternalServerErrorException: {"debug":"Cartridge return code: 1\nFailed to embed 'jenkins-client-1.4 in 'jirkotest3'\n","data":null,"api_c":["placeholder"],"result":"\nCould not add job 'jirkotest3-build' in Jenkins server:\n \nYou'll need to correct this error before attempting to embed the Jenkins client again.\n","messages":"","broker":"1.1.1","broker_c":["namespace","rhlogin","ssh","app_uuid","debug","alter","cartridge","cart_type","action","app_name","api"],"exit_code":143,"api":"1.1.1"} {code} According to the response you recieved from OpenShift, jenkins was not ready/reachable. Did you hit a temporary outage on openshift? The only other reason I can spot in the code is that the code that creates the jenkins application is not waiting for the jenkins app to become ready: ApplicationWizardModel#createApplication() does: {code} IApplication application = createApplication(name, cartridge); final boolean isApplicationAvailable = application.waitForAccessible(APP_CREATION_TIMEOUT * 1000); // blocking wait {code} whereas EmbedCartridgeWizardPageModel#createJenkinsApplication() does only (the wait is missing): {code} IApplication application = wizardModel.getUser().createApplication(name, ICartridge.JENKINS_14); // no blocking wait return application; {code} was (Author: adietish): I tried to reproduce this and could not. things went perfectly well here, I tried several times. The error log shows the following error: {code} Caused by: org.jboss.tools.openshift.express.internal.client.httpclient.InternalServerErrorException: {"debug":"Cartridge return code: 1\nFailed to embed 'jenkins-client-1.4 in 'jirkotest3'\n","data":null,"api_c":["placeholder"],"result":"\nCould not add job 'jirkotest3-build' in Jenkins server:\n \nYou'll need to correct this error before attempting to embed the Jenkins client again.\n","messages":"","broker":"1.1.1","broker_c":["namespace","rhlogin","ssh","app_uuid","debug","alter","cartridge","cart_type","action","app_name","api"],"exit_code":143,"api":"1.1.1"} {code} According to the response you recieved from OpenShift, jenkins was not ready/reachable. Did you hit a temporary outage on openshift? The only other reason I can spot in the code is that the code that creates the jenkins is not waiting for the jenkins app to become ready: ApplicationWizardModel#createApplication() does: {code} IApplication application = createApplication(name, cartridge); final boolean isApplicationAvailable = application.waitForAccessible(APP_CREATION_TIMEOUT * 1000); {code} whereas EmbedCartridgeWizardPageModel#createJenkinsApplication() does only (the wait is missing): {code} IApplication application = wizardModel.getUser().createApplication(name, ICartridge.JENKINS_14); return application; {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10502?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10502 at 12/16/11 12:10 PM: --------------------------------------------------------------------- @Pavol: I added the wait in trunk. Please try to reproduce and report back. If the reason was the missing wait, then this should not occurr in TRUNK any more. In M5 you should only experience this if you are very quick when checking the cartridges that shall be embedded. That's at least the only possible reason - beside a temporary outage of OpenShift - I can spot. was (Author: adietish): @Pavol: please try to reproduce and report back. I guess that this only occurrs if you a very quick when checking the cartridges that shall be embedded. That's at least the only possible reason - beside a temporary outage of OpenShift - I can spot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10502?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10502 at 12/16/11 12:13 PM: --------------------------------------------------------------------- @Pavol: I added the wait in TRUNK. Please try to reproduce and report back. If the reason was the missing wait, then this should not occurr in TRUNK any more. In M5 you should only experience this if you are very quick finishing the wizard that shall embed the cartridges. That's at least the only possible reason - beside a temporary outage of OpenShift - I can spot. was (Author: adietish): @Pavol: I added the wait in TRUNK. Please try to reproduce and report back. If the reason was the missing wait, then this should not occurr in TRUNK any more. In M5 you should only experience this if you are very quick when checking the cartridges that shall be embedded. That's at least the only possible reason - beside a temporary outage of OpenShift - I can spot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10502?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10502: ------------------------------------------ @Max: I dont think that the reason for the failure is the presence of a jenkins app. It could be that he ha no application slot left (5 apps quota), but even then, the wizard would fail immediately when finishing the jenkins-name-dialog, not when embedding. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10502?page=com.atlassian.jira.plugi... ] Stefan Bunciak updated JBIDE-10502: ----------------------------------- Attachment: jenkins.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10502?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10502: ------------------------------------- Attachment: jenkins-created.png mysql-jenkins-myadmin-embedded.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10502?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-10502. -------------------------------------- Resolution: Done -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10502?page=com.atlassian.jira.plugi... ] Stefan Bunciak closed JBIDE-10502. ---------------------------------- I'm sorry, i've probably hit some outage - working like a charm for me now. Closing, verified on JBoss Tools 3.3.0.Beta1c -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira