Red Hat Bugzilla – Bug 1267802
Adding Jenkins to Openshift Causes ID Error
Last modified: 2015-10-23 16:36:01 EDT
Description of problem:
I can't build using Jenkins, getting an error the instance id is repeated. I'm new to RHCloud. Using OpenShift, create a "domain," application, then choose enable Jenkins add Jenkins cartridge.
Even after deleting the Jenkins instances and re-adding them, the config.xml is missing or id is already in use.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Oct 01, 2015 1:00:58 AM INFO hudson.plugins.openshift.OpenShiftSlave createApp
Creating builder application jenkins-1 jenkinsbldr washyacht of size small in region default ...
Oct 01, 2015 1:00:58 AM INFO com.openshift.internal.client.RestService request
Requesting POST with protocol 1.2 on https://openshift.redhat.com/broker/rest/domain/washyacht/applications?include=cartridges
Oct 01, 2015 1:00:58 AM WARNING hudson.plugins.openshift.OpenShiftCloud provision
Caught com.openshift.client.OpenShiftEndpointException: Could not request https://openshift.redhat.com/broker/rest/domain/washyacht/applications?include=cartridges: An application with jenkins-1 already exists within the domain. You can only have a single application with jenkins-1 within a domain.
. Will retry 0 more times before canceling build.
Oct 01, 2015 1:01:03 AM WARNING hudson.plugins.openshift.OpenShiftCloud provision
Cancelling build due to earlier exceptions
Hi, sorry for the slow response. Are you still seeing the issue from this bug? If so, could you include more detail on the steps leading up to the failure? The Jenkins cart is domain-scoped, which means you can only have one Jenkins Server app deployed in your domain. It sounds like you're not trying to deploy multiple Jenkins server carts, though the error you're seeing is what you would get if you were to.
Is this bug still occurring?
I believe that's right and the error was multiple Jenkins apps however, I went through the steps of deleting everything and trying again (with only one) and still got the error. Honestly, it was a blocker so I've moved to Heroku for platform as a service hosting. My goal was an easy integration with Github and from Heroku, it's a click on the main dashboard, choosing allow on the Github popup, then it deploys after commits to master. Thank you though.
Still not clear what the bug was, but since the customer is no longer affected I'm closing it.
Investigation of the jenkins gear in question didn't reveal any obvious problems other than possible mis-configuration.