Bug 965560 - jenkins build job failed after recreate an app with same name
jenkins build job failed after recreate an app with same name
Status: CLOSED NOTABUG
Product: OpenShift Online
Classification: Red Hat
Component: Containers (Show other bugs)
2.x
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Dan McPherson
libra bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-21 07:05 EDT by Johnny Liu
Modified: 2015-05-14 19:19 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-05-21 15:36:02 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Johnny Liu 2013-05-21 07:05:17 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):
devenv_3253

How reproducible:
Always

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

Actual results:
Jenkins build failed, the following error is seen in console output: (http://jenkins-jialiu.dev.rhcloud.com/job/phptest-build/2/console)
<--snip-->
Cloning the remote Git repository
Cloning repository origin
ERROR: Error cloning remote repo 'origin' : Could not clone ssh://403059762629945658966016@phptest-jialiu.dev.rhcloud.com/~/git/phptest.git
ERROR: Cause: Error performing command: git clone --progress -o origin ssh://403059762629945658966016@phptest-jialiu.dev.rhcloud.com/~/git/phptest.git /var/lib/openshift/824344381751942526795776/app-root/runtime/repo
Command "git clone --progress -o origin ssh://403059762629945658966016@phptest-jialiu.dev.rhcloud.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
<--snip-->

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.



Expected results:
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.


Additional info:
Comment 1 Dan Mace 2013-05-21 15:36:02 EDT
Closing this bug and replacing it with a broker bug:

https://bugzilla.redhat.com/show_bug.cgi?id=965804

The broker bug is causing client output to be suppressed during application destroy, which explains the lack of information provided to the user.

Note You need to log in before you can comment on or make changes to this bug.