Red Hat Bugzilla – Bug 965560
jenkins build job failed after recreate an app with same name
Last modified: 2015-05-14 19:19:20 EDT
Description of problem:
Destroy an app with jenkins client embeded, recreate it with the same app name, jenkind build will fail.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Create an app named "phptest", its gear uuid is 403059762629945658966016.
2.Embed jenkins-client to this app
3.Do jenkins build successfully.
4.Destroy "phptest", then http://jenkins-jialiu.dev.rhcloud.com/job/phptest-build/ will be disabled.
5. Wait for 15min, "phptestbldr" will be deleted automatically.
6.Re-create this app, still name it "phptest", its gear uuid is 519b4e6028cd2a5d2600000c.
7.Do jenkins build again
Jenkins build failed, the following error is seen in console output: (http://jenkins-jialiu.dev.rhcloud.com/job/phptest-build/2/console)
Cloning the remote Git repository
Cloning repository origin
ERROR: Error cloning remote repo 'origin' : Could not clone ssh://email@example.com/~/git/phptest.git
ERROR: Cause: Error performing command: git clone --progress -o origin ssh://firstname.lastname@example.org/~/git/phptest.git /var/lib/openshift/824344381751942526795776/app-root/runtime/repo
Command "git clone --progress -o origin ssh://email@example.com/~/git/phptest.git /var/lib/openshift/824344381751942526795776/app-root/runtime/repo" returned status code 128: Initialized empty Git repository in /var/lib/openshift/824344381751942526795776/app-root/runtime/repo/.git/
Warning: Permanently added 'phptest-jialiu.dev.rhcloud.com,10.60.53.75' (RSA) to the list of known hosts.
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
fatal: The remote end hung up unexpectedly
Obviously it is still using previous gear user to git clone (created in step 1), that means jenkins job project is re-enabled, but not update to correct configuration.
When app with jenkins-client embedded is destroyed, its jenkins job project should be also removed. Or give some warning message to notice user to delete previous jenkins job project, and remove/re-add jenkins client again.
Closing this bug and replacing it with a broker bug:
The broker bug is causing client output to be suppressed during application destroy, which explains the lack of information provided to the user.