Description of problem: create jbossas app and embedded jenkins client to it. modify the node profile to medium.make some changes and push the build. Version-Release number of selected component (if applicable): cartridge-jenkins-1.4-0.89.3-1.git.0.7a5fab1.el6_2.noarch cartridge-jenkins-client-1.4-0.23.4-1.git.0.3eb3a5e.el6_2.noarch How reproducible: always Steps to Reproduce: 1.create jbossas app 2.create jenkins server 3.embed jenkins client to jbossas app 4.modify the node profile to medium 5.make some change and push the build Actual results: push build got failed. remote: Waiting for build to schedule................................................ remote: **BUILD FAILED/CANCELLED** remote: Please see the Jenkins log for more details via rhc-tail-files remote: !!!!!!!! remote: Deployment Halted! remote: If the build failed before the deploy step, your previous remote: build is still running. Otherwise, your application may be remote: partially deployed or inaccessible. remote: Fix the build and try again. remote: !!!!!!!! Expected results: build should be pushed without any problem. Additional info: jenkins server log： http://pastebin.test.redhat.com/84426 There is no such problem for other types of apps.
This bug does not always happen, it will often happen when you try to build with jenkins the first time, but it could be successful if you git push again to trigger the jenkins build,leave this bug open to see if there is any fix for this. The first time build error log is like following : com.openshift.express.client.OpenShiftEndpointException: Could not configure application "jbsbldr" at "https://localhost/broker/cartridge" at com.openshift.express.client.OpenShiftService.sendRequest(OpenShiftService.java:528) at com.openshift.express.client.OpenShiftService.requestApplicationAction(OpenShiftService.java:435) at com.openshift.express.client.OpenShiftService.createApplication(OpenShiftService.java:290) at hudson.plugins.openshift.OpenShiftSlave.createApp(OpenShiftSlave.java:235) at hudson.plugins.openshift.OpenShiftSlave.provision(OpenShiftSlave.java:204) at hudson.plugins.openshift.OpenShiftCloud$2.call(OpenShiftCloud.java:459) at hudson.plugins.openshift.OpenShiftCloud$2.call(OpenShiftCloud.java:451) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Caused by: com.openshift.express.internal.client.httpclient.BadRequestException: {"api_c":["placeholder"],"data":"","debug":"","broker_c":[ "namespace","rhlogin","ssh","app_uuid","debug","alter","cartridge","cart_type","action","app_name","api"],"api":"1.1.3","result":"Failed: E ither application limit has already reached or domain doesn't exist for 'xtian+t82'","messages":"","exit_code":1}
What AMI and environment are you seeing this? There is not a medium builder available for JBoss in devenvs, so it will always fail.
Hi, Bill It should be devenv_1696 or devenv_1697, we have already changed the node profile to medium , so it should not be caused short of medium builder. Thanks
Re-test this bug on devenv_1735, still failed when do jenkins build for the first time, but some symptom has changed. About the error - "Either application limit has already reached or domain doesn't exist" has been fixed in BZ#811192. The following is my steps to reflect current status: 1. Launch a devenv instance. 2. Create app with jenkins embedded. 3. Do git push to trigger jenkins build. ***The first jenkins build failed*** 4. After jenkins build failed, do git push again. ***This jenkins build succeed*** Check jenkins log, found the first failure is caused by the following error: <--snip--> Caused by: com.openshift.express.internal.client.httpclient.InternalServerErrorException: {"api":"1.1.3","api_c":["placeholder"],"messages":"\n!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\nWARNING: The 'bldr' suffix is used by the CI system (Jenkins) for its slave \nbuilders. If you create an app of this name you can't also create an app \ncalled 'phptest' and build that app in Jenkins without conflicts.\n!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\n","data":"","exit_code":1,"result":"Error communicating with DNS system. If the problem persists please contact Red Hat support.","debug":"","broker_c":["namespace","rhlogin","ssh","app_uuid","debug","alter","cartridge","cart_type","action","app_name","api"]} <--snip--> Please check attachment (jenkins.log) for more details info
Created attachment 579408 [details] jenkins.log
Looks like there was already an application of the name phptestblder - can you confirm there isn't a conflict with the existing applications? My concern is that a builder is not being cleaned up properly. I just created a new jenkins-plugin-openshift build (0.5.18) to revolve another bug so you should test with that version.
Now the version of jenkins-plugin-openshift in the latest instance (devenv_1741) is jenkins-plugin-openshift-0.5.17, after get the new jenkins-plugin-openshift build (0.5.18), I will test it again.
Re-test this issue on devenv-stage_176, it works fine now. So move it to "ON_QA".
According to comment 8, verified this bug.